From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: stable@vger.kernel.org, dhowells@redhat.com,
Matthew Wilcox <willy@infradead.org>,
Andrew W Elble <aweits@rit.edu>
Subject: Re: [PATCH] ceph: fix test for whether we can skip read when writing beyond EOF
Date: Sun, 27 Jun 2021 18:02:32 +0200 [thread overview]
Message-ID: <YNihGOegQtLR3Adf@kroah.com> (raw)
In-Reply-To: <460106c8619ce7575f84f6fb387453b31204185d.camel@kernel.org>
On Sun, Jun 27, 2021 at 11:41:45AM -0400, Jeff Layton wrote:
> On Sun, 2021-06-27 at 16:22 +0200, Greg KH wrote:
> > On Fri, Jun 25, 2021 at 01:59:51PM -0400, Jeff Layton wrote:
> > > commit 827a746f405d upstream.
> >
> > No it is not :(
> >
> > Please fix this up and resend it with the correct git id.
> >
> > thanks,
> >
>
> Are you sure?
>
> $ git log --oneline origin/master -- fs/netfs
> 827a746f405d (tag: netfs-fixes-20210621, dhowells/afs-fixes) netfs: fix test for whether we can skip read when writing beyond EOF
>
> "origin" is Linus' tree. I'm not sure what I'm doing wrong otherwise.
Commit 827a746f405d ("netfs: fix test for whether we can skip read when
writing beyond EOF") is just that, yes.
That does not match with the subject line here, or the patch itself.
So I do not understand what you are trying to do here...
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-27 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 17:59 [PATCH] ceph: fix test for whether we can skip read when writing beyond EOF Jeff Layton
2021-06-27 14:22 ` Greg KH
2021-06-27 15:41 ` Jeff Layton
2021-06-27 16:02 ` Greg KH [this message]
2021-06-27 17:22 ` Matthew Wilcox
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=YNihGOegQtLR3Adf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aweits@rit.edu \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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