From: Greg KH <gregkh@linuxfoundation.org>
To: David Sterba <dsterba@suse.cz>
Cc: colin.king@canonical.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "btrfs: remove duplicate const specifier" has been added to the 4.4-stable tree
Date: Wed, 30 Aug 2017 20:13:45 +0200 [thread overview]
Message-ID: <20170830181345.GA19575@kroah.com> (raw)
In-Reply-To: <20170830165007.GP2866@suse.cz>
On Wed, Aug 30, 2017 at 06:50:07PM +0200, David Sterba wrote:
> On Wed, Aug 30, 2017 at 05:29:36PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > btrfs: remove duplicate const specifier
> >
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > btrfs-remove-duplicate-const-specifier.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> This patch IMO does not belong to stable, it's just a cleanup and does
> not fix anything that's worth the time of anybody involved in stable trees.
On the contrary, it fixes a build warning in the tree, and having lots
of warnings hides real problems. The tree used to build "clean" with
gcc6, but now that my build systems are running gcc7, stuff like this
needs to get cleaned up again.
So this is a needed fix.
thanks,
greg k-h
prev parent reply other threads:[~2017-08-30 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 15:29 Patch "btrfs: remove duplicate const specifier" has been added to the 4.4-stable tree gregkh
2017-08-30 16:50 ` David Sterba
2017-08-30 18:13 ` Greg KH [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=20170830181345.GA19575@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=dsterba@suse.cz \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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