[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B12A780@HASMSX103.ger.corp.intel.com>
Date: Wed, 13 Jun 2012 21:09:14 +0000
From: "Winkler, Tomas" <tomas.winkler@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>
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
> > 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
Thanks
Tomas
--
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/
Powered by blists - more mailing lists