From: Chuck Lever III <chuck.lever@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Jeff Layton <jlayton@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patch in the nfsd tree
Date: Fri, 18 Aug 2023 13:29:26 +0000 [thread overview]
Message-ID: <27D91A77-C590-481B-A4AC-C0036CD175C7@oracle.com> (raw)
In-Reply-To: <20230818085423.436d3b72@canb.auug.org.au>
> On Aug 17, 2023, at 6:54 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 7f55e3c57a81 ("sunrpc: set the bv_offset of first bvec in svc_tcp_sendmsg")
>
> This is commit
>
> c96e2a695e00 ("sunrpc: set the bv_offset of first bvec in svc_tcp_sendmsg")
>
> in Linus' tree.
For the record, I've dropped 7f55e3c57a81 from nfsd-fixes. I'm at a loss
for why the commit hashes differ.
--
Chuck Lever
next prev parent reply other threads:[~2023-08-18 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 22:54 linux-next: duplicate patch in the nfsd tree Stephen Rothwell
2023-08-18 13:29 ` Chuck Lever III [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-07 21:19 Stephen Rothwell
2024-01-07 23:04 ` Chuck Lever III
2023-01-12 23:13 Stephen Rothwell
2023-01-12 23:25 ` Chuck Lever III
2023-01-16 14:33 ` Chuck Lever III
2023-01-17 0:52 ` Stephen Rothwell
2023-01-17 14:28 ` Chuck Lever III
2023-01-17 21:00 ` Stephen Rothwell
2023-01-17 21:23 ` Chuck Lever III
2023-01-17 21:48 ` Stephen Rothwell
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=27D91A77-C590-481B-A4AC-C0036CD175C7@oracle.com \
--to=chuck.lever@oracle$(echo .)com \
--cc=jlayton@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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