From: Jason Gunthorpe <jgg@ziepe.ca>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org
Subject: Re: Re: TPM legacy
Date: Mon, 3 Dec 2018 11:09:47 -0700 [thread overview]
Message-ID: <20181203180947.GD12237@ziepe.ca> (raw)
In-Reply-To: <4BE33FDA-128C-438E-8882-548B9E2848E9@gmx.de>
On Mon, Dec 03, 2018 at 07:00:26PM +0100, Peter Huewe wrote:
>
>
> Am 3. Dezember 2018 18:55:46 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>:
> >On Mon, Dec 03, 2018 at 09:55:09AM -0800, Jarkko Sakkinen wrote:
> >> On Mon, Dec 03, 2018 at 10:29:22AM -0700, Jason Gunthorpe wrote:
> >> > On Mon, Dec 03, 2018 at 04:01:38PM +0100, Peter Huewe wrote:
> >> >
> >> > > The only thing I would want to get rid of are the *1.1b based*
> >> > > drivers - they are probably end of life since quite some time.
> >The
> >> > > TIS driver&specification has been around since 2005 if not
> >longer...
> >> >
> >> > I also wanted to do this, I feel like these drivers probably don't
> >> > work any more after all the churn in the past few years..
> >>
> >> I'm with you on this but yeah, better to do it now so that it gets
> >> maximum exposure in linux-next (i.e. would land to 4.22).
> >
> >And superimportat to CC this commit also to LSM.
> >
> >/Jarkko
> Correct would be to move them to stagimg first.
> See my thread on ksummit-discuss for details.
I thought we decided not to do that anymore? Linus said just delete
them. If someone wants it back then git-revert will do the job.
If you want to do partways then flag the kconfig entries with
CONFIG_BROKEN for a cycle..
Jason
next prev parent reply other threads:[~2018-12-03 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 23:35 TPM legacy Jarkko Sakkinen
2018-12-02 15:23 ` Mimi Zohar
2018-12-02 18:29 ` James Bottomley
2018-12-02 23:13 ` Jarkko Sakkinen
2018-12-03 15:01 ` Aw: " Peter Huewe
2018-12-03 17:29 ` Jason Gunthorpe
2018-12-03 17:55 ` Jarkko Sakkinen
2018-12-03 17:55 ` Jarkko Sakkinen
2018-12-03 18:00 ` Peter Huewe
2018-12-03 18:09 ` Jason Gunthorpe [this message]
2018-12-03 18:15 ` Jarkko Sakkinen
2018-12-03 18:15 ` Jarkko Sakkinen
2018-12-03 17:30 ` Jarkko Sakkinen
2018-12-02 23:08 ` 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=20181203180947.GD12237@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=zohar@linux.ibm.com \
/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).