From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Will Deacon <will@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Paul Burton <paul.burton@mips.com>,
Sedat Dilek <sedat.dilek@gmail.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] compiler-attributes for v5.3-rc8
Date: Thu, 5 Sep 2019 10:22:32 -0700 [thread overview]
Message-ID: <CAHk-=wjBsC0bWrCy++Gzimwwfx2+3kSaac9_PbBWmH9hrWdC8g@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdm3CbZ1Uad4b8+9HU8qDgTwSFw2oqjcAvFkR8jaQQN-5g@mail.gmail.com>
On Thu, Sep 5, 2019 at 10:18 AM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> Please consider picking up just:
> https://github.com/ojeda/linux/commit/c97e82b97f4bba00304905fe7965f923abd2d755
> That lone patch is the one that fixes the particularly observed Oops.
> The rest are just cleanup; if I made that change in the more important
> patch, why not clean up the rest of the instances in the kernel?
"Why not just clean up the rest" is how bugs happen.
If it's not a fix, and it's not marked for stable (or a regression
from the merge window) it shouldn't go in this late in the rc period.
Send me _fixes_. Don't send me stuff that is "fixes plus random
cleanups that were noticed at the same time".
Linus
next prev parent reply other threads:[~2019-09-05 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 18:18 [GIT PULL] compiler-attributes for v5.3-rc8 Miguel Ojeda
2019-09-05 6:23 ` Miguel Ojeda
2019-09-05 16:20 ` Linus Torvalds
2019-09-05 17:18 ` Nick Desaulniers
2019-09-05 17:22 ` Linus Torvalds [this message]
2019-09-05 19:53 ` Miguel Ojeda
2019-09-05 19:40 ` Miguel Ojeda
2019-09-05 20:53 ` Linus Torvalds
2019-09-06 20:11 ` Miguel Ojeda
2019-09-06 22:47 ` Nick Desaulniers
2019-09-06 23:11 ` Linus Torvalds
2019-09-07 0:06 ` Nick Desaulniers
2019-09-07 0:08 ` Linus Torvalds
2019-09-07 0:45 ` Nick Desaulniers
2019-09-07 0:58 ` Linus Torvalds
2019-09-07 7:52 ` Sedat Dilek
2019-09-07 11:59 ` Miguel Ojeda
2019-09-10 8:58 ` Sedat Dilek
2019-09-10 9:16 ` Miguel Ojeda
2019-09-08 13:19 Miguel Ojeda
2019-09-08 13:24 ` Miguel Ojeda
2019-09-08 17:25 ` pr-tracker-bot
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='CAHk-=wjBsC0bWrCy++Gzimwwfx2+3kSaac9_PbBWmH9hrWdC8g@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=ndesaulniers@google.com \
--cc=paul.burton@mips.com \
--cc=sedat.dilek@gmail.com \
--cc=will@kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).