public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
	stable@vger.kernel.org, linux-xfs@vger.kernel.org,
	"Christoph Hellwig" <hch@lst.de>,
	"Brian Foster" <bfoster@redhat.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: request for inclusion of 04197b341f23 ("xfs: don't BUG() on mixed direct and mapped I/O")
Date: Tue, 25 Jul 2017 06:42:21 -0700	[thread overview]
Message-ID: <20170725134221.GB19075@kroah.com> (raw)
In-Reply-To: <18dc98f7-abd8-4925-a303-7ae4c1e46db5@suse.com>

On Tue, Jul 25, 2017 at 01:44:30PM +0300, Nikolay Borisov wrote:
> 
> 
> On 25.07.2017 13:43, Holger Hoffstätte wrote:
> > On 07/25/17 08:47, Nikolay Borisov wrote:
> >> I'd like to request the aforementioned patch to be included into stable
> >> kernels. I've attached the 4.4 backport, the patch got introduced in
> >> 4.10 so for 4.9 it will likely be able to apply cleanly, for 4.4 it
> >> needed a bit of adjustment.
> > 
> > It has been in 4.9-stable since January, see:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/fs/xfs?h=linux-4.9.y&id=3978c5bb004312fd267aed7279fe64b119e126b0
> > 
> 
> Strange, it's missing a stable tag

What does that have to do with anything?  Lots of patches get asked to
be included that don't have stable tags, just like you just did :)

Also, please always include the original git commit id of the patch you
wish to have included with your request so that I don't have to turn
around and ask for it...

thanks,

greg k-h

  reply	other threads:[~2017-07-25 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  6:47 request for inclusion of 04197b341f23 ("xfs: don't BUG() on mixed direct and mapped I/O") Nikolay Borisov
2017-07-25 10:43 ` Holger Hoffstätte
2017-07-25 10:44   ` Nikolay Borisov
2017-07-25 13:42     ` Greg KH [this message]
2017-07-25 13:43       ` Greg KH
2017-07-25 13:47         ` Greg KH
2017-07-25 13:50           ` Christoph Hellwig
2017-07-25 14:02             ` Nikolay Borisov
2017-07-25 15:45               ` Darrick J. Wong

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=20170725134221.GB19075@kroah.com \
    --to=greg@kroah.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=hch@lst.de \
    --cc=holger@applied-asynchrony.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --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