linux-kernel - Re: [Tpctl-users] Inclusion of tp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081118171350.GA13671@atrey.karlin.mff.cuni.cz>
Date:	Tue, 18 Nov 2008 18:13:51 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Miklos Szeredi <miklos@...redi.hu>, hpa@...or.com,
	multinymous@...il.com, jrm8005@...il.com,
	tpctl-users@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [Tpctl-users] Inclusion of tp_smapi module into kernel?

> On Mon, 17 Nov 2008, Miklos Szeredi wrote:
> > On Mon, 17 Nov 2008, H. Peter Anvin wrote:
> > > Shem Multinymous wrote:
> > > > On Mon, Nov 17, 2008 at 12:13 PM, J.R. Mauro <jrm8005@...il.com> wrote:
> > > >> There are several utilities maintained by this author, and finding
> > > >> some way to merge the code has been tried more than once. If you look
> > > >> back far enough, Andrew asked to have another of the project's members
> > > >> sign off on the patch, and maybe that would be acceptable enough, but
> > > >> afaik the author has never responded directly to that idea.
> > > > 
> > > > We've discussed that in private at the time, and recently on LKML too.
> > > > In summary:
> > > > I'm fine with that, and so is everybody I talked to (including Linus),
> > > > except Greg KH who vetoed it since he believes the code is irrevocably
> > > > and contagiously evil.
> > > > 
> > > 
> > > Signed-off-by is about copyright, it's not a review issue.  It means "I 
> > > certify that I know that the author had the rights to submit this code." 
> > >    Code quality is important but separate.
> > 
> > We've discussed this issue on the internal suse mailing lists, and
> > concluded that the solution is simple: someone from IBM, Lenovo or
> > whoever they license the technology from should sign off on the code.
> 
> That would be nice, yes.
> 
> > But implementing this got stuck at some stage.
> > 
> > Can anybody help with info about who's responsible for this part of
> > the ThinkPad?
> 
> SuSE has direct management-level and engineering-level contacts with the
> Lenovo team responsible for the ThinkPad.  IMO, the contact needs to be done
> through those channels (which are Linux-friendly).
> 
> If SuSE decided not to do it, they must have had their reasons.  I wouldn't
> know them, but I can guess as much as anyone else, and my pet guess is that
> they are waiting for an opportune time.

SuSE asked, Lenovo said no. We can probably try again...
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/