stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: cel@kernel.org, stable@vger.kernel.org,
	linux-nfs@vger.kernel.org,
	Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: [PATCH] Revert 2267b2e84593bd3d61a1188e68fba06307fa9dab
Date: Wed, 17 Apr 2024 15:25:09 +0200	[thread overview]
Message-ID: <2024041745-stagnate-bloating-87e0@gregkh> (raw)
In-Reply-To: <Zh/LyjplA5coHKqJ@tissot.1015granger.net>

On Wed, Apr 17, 2024 at 09:16:58AM -0400, Chuck Lever wrote:
> On Wed, Apr 17, 2024 at 07:56:53AM +0200, Greg KH wrote:
> > On Tue, Apr 16, 2024 at 04:33:37PM -0400, cel@kernel.org wrote:
> > > From: Chuck Lever <chuck.lever@oracle.com>
> > > 
> > > ltp test fcntl17 fails on v5.15.154. This was bisected to commit
> > > 2267b2e84593 ("lockd: introduce safe async lock op").
> > 
> > Your subject line is a big odd :(
> 
> I used the style we normally use for revert patches for Linus'
> kernel. Let me know what needs to be improved.

That's not normal, this is what that would normally look like:
~/linux/stable/scratch (s-515) $ git revert 2267b2e84593bd3d61a1188e68fba06307fa9dab
Auto-merging fs/nfsd/nfs4state.c
[s-515 5bd6c14e1a72] Revert "lockd: introduce safe async lock op"
 4 files changed, 6 insertions(+), 29 deletions(-)

Subject lines don't have a huge hash in it.

Anyway, I can fix this up, no worries, but I don't know how you created
this to get that subject line.

thanks,

greg k-h

  reply	other threads:[~2024-04-17 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 20:33 [PATCH] Revert 2267b2e84593bd3d61a1188e68fba06307fa9dab cel
2024-04-17  5:56 ` Greg KH
2024-04-17 13:16   ` Chuck Lever
2024-04-17 13:25     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-16 20:20 cel
2024-04-16 20:24 ` kernel test robot

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=2024041745-stagnate-bloating-87e0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).