From: Yuki Machida <machida.yuki@jp.fujitsu.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: stable@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: please back port a patch of warning fix to v4.1.y
Date: Wed, 15 Jun 2016 17:38:37 +0900 [thread overview]
Message-ID: <5761140D.4010103@jp.fujitsu.com> (raw)
In-Reply-To: <57608234.1030801@oracle.com>
Hi Sasha,
>> I conformed that v4.1.26 has a same warning using gcc 5.2.0.
>> Please apply following patch to 4.1.y.
>> 10fbd36e362a0f367e34a7cd876a81295d8fc5ca
>
> Same as the other one, this looks like it just stops the warning rather
> than fix an actual bug, which means it's not really -stable material.
Thank you for advice.
I think that it is a patch for a warning fix, not actual bug fix.
Therefore, I want to cancel the request.
I will read stable_kernel_rules.txt again.
Thanks,
Yuki Machida
prev parent reply other threads:[~2016-06-15 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 9:55 please back port a patch of warning fix to v4.1.y Yuki Machida
2016-06-14 22:16 ` Sasha Levin
2016-06-15 8:38 ` Yuki Machida [this message]
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=5761140D.4010103@jp.fujitsu.com \
--to=machida.yuki@jp.fujitsu.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).