linux-kernel - Re: misc: mei: fixes for 3.5

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: <20120613214509.GA9051@kroah.com>
Date:	Wed, 13 Jun 2012 14:45:09 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"Winkler, Tomas" <tomas.winkler@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"alan@...ux.intel.com" <alan@...ux.intel.com>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>
Subject: Re: misc: mei: fixes for 3.5

On Wed, Jun 13, 2012 at 09:09:14PM +0000, Winkler, Tomas wrote:
> 
> 
> > > Hi Greg,
> > > please consider this batch for queuing into 3.5 1. patch 2/4 bug in
> > > probe: visible only after merging with the trunk 2. patch 3/4 fixes
> > > kernel oops that was revealed when probe failed 3. patch 4/4 is
> > > regression fix and should be merged also to stable 3.4 4. patch 1/4 is
> > > a minor documentation fix
> > 
> > Grammer fixes are not ok for 3.5 at this point in time, sorry.  I'll queue up the
> > other 3 though.
> 
> Thanks reasonable. 
> 
> Please consider also  this two:
> 
> This one is one more fix connected to the same issue as the 3 patches. (From Samuel Oritz) 
> http://marc.info/?l=linux-kernel&m=133940653731271&w=2
> 
> This one is just adding a flag to WATCHDOG devices that was only possible after merging the watchdog tree into 3.5-rc1. 
> This one is not must so I leave it for you to decide. 
> http://marc.info/?l=linux-kernel&m=133940653831272&w=2

Yes, they are still in my queue, I'll get to them...

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/