From: Christoph Hellwig <hch@infradead.org>
To: NeilBrown <neilb@suse.de>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/2] nfsd: fix handling of error from unshare_fs_struct()
Date: Mon, 29 Jul 2024 15:01:13 -0700 [thread overview]
Message-ID: <ZqgRKU7rYXo4ncEG@infradead.org> (raw)
In-Reply-To: <172228724989.18529.183021144838147324@noble.neil.brown.name>
On Tue, Jul 30, 2024 at 07:07:29AM +1000, NeilBrown wrote:
> > Also, 1/2 is From: your brown.name account, but the SoB is your
> > SuSE email. (Maybe that doesn't matter).
>
> Probably don't matter. That happened because I wrote that patch on my
> notebook instead of my desktop and they have different defaults. I'll
> try to remember that for next time.
The signoff is supposed to match the author address. If you send it
out using a different email account you need to add a separate From:
line to the mail body. git-send-email will do that automatically for
you.
next prev parent reply other threads:[~2024-07-29 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 2:18 [PATCH 0/2] nfsd: fix handling of error from unshare_fs_struct() NeilBrown
2024-07-29 2:18 ` [PATCH 1/2] sunrpc: merge svc_rqst_alloc() into svc_prepare_thread() NeilBrown
2024-07-29 2:18 ` [PATCH 2/2] sunrpc: allow svc threads to fail initialisation cleanly NeilBrown
2024-07-29 12:44 ` [PATCH 0/2] nfsd: fix handling of error from unshare_fs_struct() Jeff Layton
2024-07-29 14:36 ` Chuck Lever
2024-07-29 21:07 ` NeilBrown
2024-07-29 21:25 ` Chuck Lever III
2024-07-29 23:17 ` NeilBrown
2024-07-29 22:01 ` Christoph Hellwig [this message]
2024-07-30 0:43 ` NeilBrown
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=ZqgRKU7rYXo4ncEG@infradead.org \
--to=hch@infradead.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.com \
/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