public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Chuck Lever <cel@kernel.org>,
	"stable@kernel.org" <stable@kernel.org>,
	Vasily Gorbik <gor@linux.ibm.com>,
	linux-stable <stable@vger.kernel.org>,
	Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH 6.8.y] NFSD: fix endianness issue in nfsd4_encode_fattr4
Date: Tue, 23 Apr 2024 09:34:57 -0700	[thread overview]
Message-ID: <2024042342-comic-reverend-1dd5@gregkh> (raw)
In-Reply-To: <70538016-22BC-4D71-8DBC-4832AB60E6BB@oracle.com>

On Tue, Apr 23, 2024 at 04:30:38PM +0000, Chuck Lever III wrote:
> 
> 
> > On Apr 23, 2024, at 12:26 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > 
> > On Fri, Apr 19, 2024 at 12:03:15PM -0400, cel@kernel.org wrote:
> >> From: Vasily Gorbik <gor@linux.ibm.com>
> >> 
> >> [ Upstream commit 862bee84d77fa01cc8929656ae77781abf917863 ]
> > 
> > that commit is in 6.7, so why would we need to add it to 6.8?
> 
> Copy-paste error. Try f488138b526715c6d2568d7329c4477911be4210
> instead.

Can it be sent with the correct one so I don't have to hand-edit this?

thanks,

greg k-h

  reply	other threads:[~2024-04-23 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 10:37 FAILED: patch "[PATCH] NFSD: fix endianness issue in nfsd4_encode_fattr4" failed to apply to 6.8-stable tree gregkh
2024-04-19 16:03 ` [PATCH 6.8.y] NFSD: fix endianness issue in nfsd4_encode_fattr4 cel
2024-04-23 16:26   ` Greg KH
2024-04-23 16:30     ` Chuck Lever III
2024-04-23 16:34       ` Greg KH [this message]
2024-04-23 16:37 ` cel
2024-04-23 16:46   ` Greg KH

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=2024042342-comic-reverend-1dd5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=gor@linux.ibm.com \
    --cc=jlayton@kernel.org \
    --cc=stable@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