linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olga Kornievskaia <kolga@netapp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the nfsd tree
Date: Fri, 21 May 2021 09:50:51 -0400	[thread overview]
Message-ID: <20210521135051.GA30314@fieldses.org> (raw)
In-Reply-To: <20210521080416.45f06cb8@canb.auug.org.au>

On Fri, May 21, 2021 at 08:04:16AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Commit
> 
>   ff78b9442926 ("NFSD add vfs_fsync after async copy is done")
> 
> is missing a Signed-off-by from its author.

Olga, can I add

	Signed-off-by: Olga Kornievskaia <kolga@netapp.com>

?

--b.

  reply	other threads:[~2021-05-21 13:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 22:04 linux-next: Signed-off-by missing for commit in the nfsd tree Stephen Rothwell
2021-05-21 13:50 ` J. Bruce Fields [this message]
2021-05-21 13:55   ` Kornievskaia, Olga
2021-05-21 14:01     ` J. Bruce Fields
2021-05-21 14:42       ` Kornievskaia, Olga
2021-05-21 14:53         ` J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22 21:15 Stephen Rothwell
2020-11-08 21:20 Stephen Rothwell
2020-11-08 21:29 ` J. Bruce Fields
2020-11-09  9:15   ` Dan Carpenter
2019-12-21  3:10 Stephen Rothwell
2019-12-02 20:38 Stephen Rothwell
2017-11-27 22:52 Stephen Rothwell
2017-11-28  1:38 ` J. Bruce Fields
2017-11-28  2:02   ` Stephen Rothwell
2017-11-09 19:51 Stephen Rothwell
2017-11-09 20:06 ` J. Bruce Fields
2017-08-24 22:48 Stephen Rothwell
2017-08-25  2:21 ` J. Bruce Fields
2017-08-25  2:37   ` J. Bruce Fields

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=20210521135051.GA30314@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kolga@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).