All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolay Borisov <nborisov@suse.com>
Cc: stable@vger.kernel.org, linux-xfs@vger.kernel.org,
	Brian Foster <bfoster@redhat.com>,
	darrick.wong@oracle.com, asavkov@redhat.com
Subject: Re: Request for inclusion of b54554ac5afa ("Make __xfs_xattr_put_listen preperly report errors.")
Date: Mon, 12 Jun 2017 14:59:23 +0200	[thread overview]
Message-ID: <20170612125923.GA12197@kroah.com> (raw)
In-Reply-To: <a59171e2-9962-00c6-977f-45b668ca96c6@suse.com>

On Mon, Jun 12, 2017 at 03:40:08PM +0300, Nikolay Borisov wrote:
> 
> 
> On 12.06.2017 15:33, Greg KH wrote:
> > On Mon, Jun 12, 2017 at 10:24:16AM +0300, Nikolay Borisov wrote:
> >> Hello,
> >>
> >> I'd like to request the inclusion of the aforementioned patch.
> > 
> > What patch?  Commit b54554ac5afa is not in any kernel tree that I can
> > find :(
> 
> Yeah, I tested this particular patch but I might have copied the ID from
> an internal tree. The upstream patch is:
> 
> 791cc43b36eb ("Make __xfs_xattr_put_listen preperly report errors.")
> 
> It's a single one-liner and it applies cleanly on 4.4

Ok, thanks, please be more careful next time...

now queued up.

greg k-h

  reply	other threads:[~2017-06-12 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12  7:24 Request for inclusion of b54554ac5afa ("Make __xfs_xattr_put_listen preperly report errors.") Nikolay Borisov
2017-06-12  7:44 ` Greg KH
2017-06-12  7:46   ` Nikolay Borisov
2017-06-12 12:33 ` Greg KH
2017-06-12 12:40   ` Nikolay Borisov
2017-06-12 12:59     ` Greg KH [this message]
2017-06-12 12:47   ` Artem Savkov

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=20170612125923.GA12197@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=asavkov@redhat.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.