linux-kernel - Re: [GIT PATCH] driver core patches for 3.5-rc1

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] [day] [month] [year] [list]

Date:	Tue, 22 May 2012 23:12:16 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Kay Sievers <kay@...y.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] driver core patches for 3.5-rc1 - try 2

On Tue, May 22, 2012 at 03:12:16PM -0700, Joe Perches wrote:
> On Tue, 2012-05-22 at 15:05 -0700, Greg KH wrote:
> > On Tue, May 22, 2012 at 02:58:47PM -0700, Joe Perches wrote:
> > > How is it really better that what is available now?
> > > 
> > > Perhaps it would be better to respin all the
> > > printk modifications without adding [v]printk_emit
> > > and have the [v]printk_emit bits debated a bit more.
> > 
> > I'm always glad to review patches, but to just propose something that
> > works to be reverted without a patch to replace the functionality, isn't
> > ok.
> 
> It hasn't been committed yet in anything other than
> -next.
> 
> Lots of stuff gets committed there and later removed
> and hits Linus' mainline tree.

Sorry, but as people are "downstream" for me, I do not rebase my trees,
unless something really bad happened (i.e. I messed up the tree).  So
this will not happen, sorry.

Also, the patches are all in Linus's tree now, so the point is moot.

thanks,

greg k-h
--
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/