From: Andrew Morton <akpm@linux-foundation.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wenyu Huang <huangwenyu5@huawei.com>,
pmladek@suse.com, rostedt@goodmis.org, linux@rasmusvillemoes.dk,
senozhatsky@chromium.org, linux-next@vger.kernel.org,
gustavoars@kernel.org
Subject: Re: [PATCH next] Fix the build failed caused by -Wstringop-overflow
Date: Thu, 30 Nov 2023 13:23:15 -0800 [thread overview]
Message-ID: <20231130132315.6725198ba178b071eb7729c5@linux-foundation.org> (raw)
In-Reply-To: <c3167ae2-fd98-4e68-9112-cfdfbb34b87b@embeddedor.com>
On Thu, 30 Nov 2023 12:04:28 -0600 "Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
> > On top of that, Fixes tag is not enough to get it to stable. See the rules
> > on how to submit a material to stable kernels, it's in the documentation.
>
> We are talking about different things. I'm talking about commit IDs staying
> unchanged (stable commit IDs). That's different to stable kernels. :)
That's why we use the
04448A0E ("wobble the fronnozzle")
format. Searching for the title is the fallback option.
And I agree with what appears to be everyone else. Always include the
Fixes: if possible. So that people don't accidentally cherrypick a
known-to-be-broken patch.
next prev parent reply other threads:[~2023-11-30 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 10:57 [PATCH next] Fix the build failed caused by -Wstringop-overflow Wenyu Huang
2023-11-30 15:52 ` Gustavo A. R. Silva
2023-11-30 17:48 ` Andy Shevchenko
2023-11-30 17:50 ` Andy Shevchenko
2023-11-30 18:04 ` Gustavo A. R. Silva
2023-11-30 18:06 ` Andy Shevchenko
2023-11-30 18:13 ` Gustavo A. R. Silva
2023-11-30 21:23 ` Andrew Morton [this message]
2023-11-30 17:56 ` Gustavo A. R. Silva
2023-11-30 18:05 ` Andy Shevchenko
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=20231130132315.6725198ba178b071eb7729c5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=huangwenyu5@huawei.com \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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).