All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the nfsd tree
Date: Thu, 24 Aug 2017 22:21:41 -0400	[thread overview]
Message-ID: <20170825022141.GB26099@fieldses.org> (raw)
In-Reply-To: <20170825084821.2870bbb7@canb.auug.org.au>

On Fri, Aug 25, 2017 at 08:48:21AM +1000, Stephen Rothwell wrote:
> Hi Bruce,
> 
> Commit
> 
>   1b7f1a85c0fa ("opdesc will be useful outside nfs4proc.c")
> 
> is missing a Signed-off-by from its author and committer.

Fixed, thanks.--b.

  reply	other threads:[~2017-08-25  2:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 22:48 linux-next: Signed-off-by missing for commit in the nfsd tree Stephen Rothwell
2017-08-25  2:21 ` J. Bruce Fields [this message]
2017-08-25  2:37   ` J. Bruce Fields
2017-11-09 19:51 Stephen Rothwell
2017-11-09 20:06 ` J. Bruce Fields
2017-11-27 22:52 Stephen Rothwell
2017-11-28  1:38 ` J. Bruce Fields
2017-11-28  2:02   ` Stephen Rothwell
2018-02-22  4:17 Stephen Rothwell
     [not found] ` <12138EE4-77CA-480F-B2F9-B4C7E4E20891@ettle.org.uk>
2018-02-23  1:05   ` J. Bruce Fields
2018-02-23 12:41     ` James Ettle
2018-02-23 15:20       ` J. Bruce Fields
2019-12-02 20:38 Stephen Rothwell
2019-12-21  3:10 Stephen Rothwell
2020-11-08 21:20 Stephen Rothwell
2020-11-08 21:29 ` J. Bruce Fields
2020-11-09  9:15   ` Dan Carpenter
2021-05-20 22:04 Stephen Rothwell
2021-05-21 13:50 ` J. Bruce Fields
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
2021-11-22 21:15 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=20170825022141.GB26099@fieldses.org \
    --to=bfields@fieldses.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.