public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 nfs tree
Date: Mon, 14 Jul 2025 15:29:18 -0700	[thread overview]
Message-ID: <95bc7cef0dab4545084b57f53194afd336badee9.camel@gmail.com> (raw)
In-Reply-To: <20250715075840.319506f1@canb.auug.org.au>

On Tue, 2025-07-15 at 07:58 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Commits
> 
>   66843cd7622c ("NFS: remove unused pnfs_ld_data field from struct
> nfs_server")
>   7665e5928005 ("NFS: remove unused time_delta field from struct
> nfs_server")
>   747ee5683b9b ("NFS: remove unused wpages field from struct
> nfs_server")
>   8eb52d5f0c1e ("pnfs: add pnfs_ds_connect trace point")
> 
> are missing a Signed-off-by from their committer.

Thanks! I clearly need to be more consistent when using the "b4"
utility to download these patches.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com

  reply	other threads:[~2025-07-14 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 21:58 linux-next: Signed-off-by missing for commit in the nfs tree Stephen Rothwell
2025-07-14 22:29 ` Trond Myklebust [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-30 21:26 Stephen Rothwell
2018-05-30 22:22 ` Trond Myklebust
2018-05-30 22:26   ` Trond Myklebust
2018-05-31  0:42     ` Stephen Rothwell
2018-05-31  5:24   ` 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=95bc7cef0dab4545084b57f53194afd336badee9.camel@gmail.com \
    --to=trondmy@gmail.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