From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
pjaroszynski@nvidia.com, william.kucharski@oracle.com,
stable@vger.kernel.org, hch@lst.de, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] iomap: Revert "fs/iomap.c: get/put the page in iomap_page_create/release()"
Date: Fri, 21 Dec 2018 08:40:42 +0100 [thread overview]
Message-ID: <20181221074042.GA8633@kroah.com> (raw)
In-Reply-To: <20181220205721.GD4205@dastard>
On Fri, Dec 21, 2018 at 07:57:21AM +1100, Dave Chinner wrote:
> On Thu, Dec 20, 2018 at 01:28:25PM +0100, Greg KH wrote:
> > On Thu, Dec 20, 2018 at 11:23:24PM +1100, Dave Chinner wrote:
> > > From: Dave Chinner <dchinner@redhat.com>
> > >
> > > This reverts commit 61c6de667263184125d5ca75e894fcad632b0dd3.
>
> <snip>
>
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read:
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> >
> > </formletter>
>
> This wasn't a stable kernel patch submission. This was to let the
> stable kernel maintainers know that a commit that was submitted for
> stable kernel inclusion (via a cc stable in the commit message) is
> buggy and should not be backported. i.e. if you've already queued/
> backported 61c6de6672 then you need to drop it from your trees.
As the commit 61c6de667263 ("fs/iomap.c: get/put the page in
iomap_page_create/release()") was tagged for a stable release (and is in
4.19.11) it would be nice to also add the cc: stable in the revert.
When you just blindly send it to the stable mailing list, we have no
idea what to do with it, hence the automated form letter that was sent.
Now that this is in Linus's tree, I'll dig out the revert and remember
to queue it up for the next round of stable updates, thanks for letting
us know.
greg k-h
next prev parent reply other threads:[~2018-12-21 7:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 12:23 [PATCH] iomap: Revert "fs/iomap.c: get/put the page in iomap_page_create/release()" Dave Chinner
2018-12-20 12:28 ` Greg KH
2018-12-20 20:57 ` Dave Chinner
2018-12-21 7:40 ` Greg KH [this message]
2018-12-21 22:06 ` Eric Sandeen
2018-12-22 0:04 ` Sasha Levin
2018-12-20 17:41 ` Christoph Hellwig
2018-12-20 20:53 ` Dave Chinner
2018-12-20 22:42 ` Linus Torvalds
2018-12-21 9:39 ` Christoph Hellwig
2018-12-21 19:18 ` Linus Torvalds
2018-12-21 19:20 ` Christoph Hellwig
2018-12-21 19:26 ` Linus Torvalds
2018-12-21 21:58 ` Dave Chinner
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=20181221074042.GA8633@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pjaroszynski@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=william.kucharski@oracle.com \
/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).