From: Jason Gunthorpe <jgg@ziepe.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
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 tpmdd tree
Date: Fri, 29 Dec 2017 19:57:07 -0700 [thread overview]
Message-ID: <20171230025707.GI6513@ziepe.ca> (raw)
In-Reply-To: <20171230103213.5b596192@canb.auug.org.au>
On Sat, Dec 30, 2017 at 10:32:13AM +1100, Stephen Rothwell wrote:
> Hi Jarkko,
>
> Commit
>
> c01386d6129f ("tpm: Update MAINTAINERS for Jason Gunthorpe")
>
> is missing a Signed-off-by from its committer.
Thanks Stephen,
Jarkko, it started out OK, so you can probably just add it back in?
https://www.spinics.net/lists/linux-integrity/msg00581.html
Jason
next prev parent reply other threads:[~2017-12-30 2:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 23:32 linux-next: Signed-off-by missing for commit in the tpmdd tree Stephen Rothwell
2017-12-30 2:57 ` Jason Gunthorpe [this message]
2018-01-02 15:33 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
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
2018-10-30 22:16 Stephen Rothwell
2018-11-01 14:23 ` 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=20171230025707.GI6513@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=jarkko.sakkinen@linux.intel.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).