From: Timothy Pearson <tpearson@raptorengineering.com> To: Michael Ellerman <mpe@ellerman.id.au> Cc: Jens Axboe <axboe@kernel.dk>, regressions <regressions@lists.linux.dev>, npiggin <npiggin@gmail.com>, christophe leroy <christophe.leroy@csgroup.eu>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH v2] powerpc: Don't clobber fr0/vs0 during fp|altivec register save Date: Mon, 27 Nov 2023 12:39:14 -0600 (CST) [thread overview] Message-ID: <1276384468.50536225.1701110354677.JavaMail.zimbra@raptorengineeringinc.com> (raw) In-Reply-To: <1340817182.49635143.1700784119445.JavaMail.zimbra@raptorengineeringinc.com> Just wanted to check back and see if this patch was going to be queued up soon? We're still having to work around / advertise the data destruction issues the underlying bug is causing on e.g. Debian Stable. Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Timothy Pearson <tpearson@raptorengineering.com> To: Michael Ellerman <mpe@ellerman.id.au> Cc: Jens Axboe <axboe@kernel.dk>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, regressions <regressions@lists.linux.dev>, npiggin <npiggin@gmail.com> Subject: Re: [PATCH v2] powerpc: Don't clobber fr0/vs0 during fp|altivec register save Date: Mon, 27 Nov 2023 12:39:14 -0600 (CST) [thread overview] Message-ID: <1276384468.50536225.1701110354677.JavaMail.zimbra@raptorengineeringinc.com> (raw) In-Reply-To: <1340817182.49635143.1700784119445.JavaMail.zimbra@raptorengineeringinc.com> Just wanted to check back and see if this patch was going to be queued up soon? We're still having to work around / advertise the data destruction issues the underlying bug is causing on e.g. Debian Stable. Thanks!
next prev parent reply other threads:[~2023-11-27 18:39 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-19 15:18 [PATCH v2] powerpc: Don't clobber fr0/vs0 during fp|altivec register save Timothy Pearson 2023-11-20 7:10 ` Michael Ellerman 2023-11-20 14:32 ` Nicholas Piggin 2023-11-20 16:45 ` Timothy Pearson 2023-11-20 16:45 ` Timothy Pearson 2023-11-20 23:39 ` Michael Ellerman 2023-11-20 23:39 ` Michael Ellerman 2023-11-21 0:27 ` Nicholas Piggin 2023-11-21 0:27 ` Nicholas Piggin 2023-11-21 1:23 ` Timothy Pearson 2023-11-21 1:23 ` Timothy Pearson 2023-11-21 7:56 ` Nicholas Piggin 2023-11-21 7:56 ` Nicholas Piggin 2023-11-21 4:10 ` Timothy Pearson 2023-11-21 4:10 ` Timothy Pearson 2023-11-21 4:26 ` Timothy Pearson 2023-11-21 4:26 ` Timothy Pearson 2023-11-21 7:54 ` Nicholas Piggin 2023-11-21 7:54 ` Nicholas Piggin 2023-11-22 5:01 ` Michael Ellerman 2023-11-22 5:01 ` Michael Ellerman 2023-11-24 0:01 ` Timothy Pearson 2023-11-24 0:01 ` Timothy Pearson 2023-11-27 18:39 ` Timothy Pearson [this message] 2023-11-27 18:39 ` Timothy Pearson 2023-11-27 19:58 ` Christophe Leroy 2023-11-27 19:58 ` Christophe Leroy 2023-11-28 0:59 ` Michael Ellerman 2023-11-28 0:59 ` Michael Ellerman 2023-11-28 1:40 ` Nicholas Piggin 2023-11-28 1:40 ` Nicholas Piggin 2023-11-27 22:53 ` Michael Ellerman 2023-11-27 22:53 ` Michael Ellerman 2023-11-28 12:57 ` Michael Ellerman 2023-11-28 12:57 ` Michael Ellerman 2023-11-30 16:29 ` Timothy Pearson 2023-11-30 16:29 ` Timothy Pearson 2023-11-21 0:18 ` Nicholas Piggin 2023-11-21 0:18 ` Nicholas Piggin 2023-12-02 23:00 ` Michael Ellerman
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1276384468.50536225.1701110354677.JavaMail.zimbra@raptorengineeringinc.com \ --to=tpearson@raptorengineering.com \ --cc=axboe@kernel.dk \ --cc=christophe.leroy@csgroup.eu \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ --cc=npiggin@gmail.com \ --cc=regressions@lists.linux.dev \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.