linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the tpmdd tree
Date: Wed, 31 Oct 2018 09:16:42 +1100	[thread overview]
Message-ID: <20181031091642.6ca5943b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 164 bytes --]

Hi Jarkko,

Commit

  e22bf023c141 ("tpm: tpm_ibmvtpm: fix kdoc warnings")

is missing a Signed-off-by from its committer.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2018-10-30 22:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 22:16 Stephen Rothwell [this message]
2018-11-01 14:23 ` linux-next: Signed-off-by missing for commit in the tpmdd tree Jarkko Sakkinen
  -- strict thread matches above, loose matches on Subject: below --
2025-03-17 21:17 Stephen Rothwell
2025-03-20  9:17 ` Jarkko Sakkinen
2025-03-10 21:11 Stephen Rothwell
2025-03-11  9:38 ` Jarkko Sakkinen
2024-08-01 23:02 Stephen Rothwell
2024-08-02 17:57 ` Jarkko Sakkinen
2024-08-02 19:21   ` Jarkko Sakkinen
2023-01-26 22:59 Stephen Rothwell
2023-02-07 23:25 ` Jarkko Sakkinen
2022-01-06 21:38 Stephen Rothwell
2022-01-08 22:19 ` Jarkko Sakkinen
2020-06-17 23:52 Stephen Rothwell
2020-06-18  7:10 ` Jarkko Sakkinen
2020-06-17  4:56 Stephen Rothwell
2020-06-17 23:30 ` Jarkko Sakkinen
2019-09-01 21:32 Stephen Rothwell
2019-09-02 13:58 ` Jarkko Sakkinen
2017-12-29 23:32 Stephen Rothwell
2017-12-30  2:57 ` Jason Gunthorpe
2018-01-02 15:33 ` Jarkko Sakkinen
2017-09-26 23:25 Stephen Rothwell
2017-09-29 16:57 ` Jarkko Sakkinen

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=20181031091642.6ca5943b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).