From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] security subsytem: TPM changes for v5.2
Date: Fri, 10 May 2019 08:19:55 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1905100819390.13541@namei.org> (raw)
In-Reply-To: <CAHk-=whqzNFfeNOouBjH2GKMVgMi22fsNOaCgbUOnCPmKmEXeQ@mail.gmail.com>
On Thu, 9 May 2019, Linus Torvalds wrote:
> On Thu, May 9, 2019 at 10:23 AM James Morris <jmorris@namei.org> wrote:
> >
> > Bugfixes and new selftests for v5.1 features (partial reads in /dev/tpm0).
>
> What the heck is going on?
>
> I got all of these long ago in the "TPM fixes" branch for 5.1. One
> month ago, merge commit a556810d8e06.
>
> These are just rebased (!) copies of stuff I already have, and they should
>
> (a) never have been rebased in the first place
>
> (b) certainly not be re-sent to me as a new branch
>
> Please throw this branch away and make sure it really is dead and
> buried and never shows up again.
Yikes, ok.
> And take a moment to look at what happened and why this broken branch
> was duplicated and sent twice!
Could it be something I pulled in? I haven't used 'rebase' in many years.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2019-05-09 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 17:23 [GIT PULL] security subsytem: TPM changes for v5.2 James Morris
2019-05-09 19:53 ` Linus Torvalds
2019-05-09 22:19 ` James Morris [this message]
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=alpine.LRH.2.21.1905100819390.13541@namei.org \
--to=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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