On Mon, Jun 27, 2011 at 2:42 PM, Rolf Eike Beer <eike-kernel@xxxxxxxxx> wrote: > Rolf Eike Beer wrote: >> Am Freitag, 18. März 2011, 17:39:57 schrieb Rolf Eike Beer: >> > Am Mittwoch, 2. März 2011, 21:19:24 schrieb Jesse Brandeburg: >> > > On Mon, Feb 28, 2011 at 5:40 AM, Guy Martin <gmsoft@xxxxxxxxxxxx> wrote: >> > > > Hi Jeff, >> > > > >> > > > Any luck getting this into mainline ? >> > > >> > > Hi Guy, sorry for the delay, >> > > We haven't been able to get our contacts in HP to give us a decent >> > > response so far, we are following up with them to see whats up. We >> > > have not lost the patch and are still tracking it internally. >> > > >> > > Give us a couple more weeks if that is okay and we should be able to >> > > settle this by then. >> > >> > I wonder what exactly you are waiting for? This is a sanity check that >> > we >> > disable, so no working systems could get broken by this. And every >> > single >> > C8000 seems to be affected by this and is working fine with that patch. >> > So maybe people at HP might have a clue _why_ this is screwed, but >> > until then I don't see any point in waiting. >> > >> > So please just add my tested-by and push this upstream soon. Since this >> > is basically a hardware quirk I would like to get this into stable also >> > so we may run vanilla 2.6.38.1 or something like that on C8000. >> > >> > Tested-by: Rolf Eike Beer <eike-kernel@xxxxxxxxx> >> >> For the netdev folks: it's this patch we are talking about >> >> http://www.spinics.net/lists/linux-parisc/msg03091.html >> >> I would love to see that someone finally picks this up and pushes this >> upstream, CC stable. This is absolutely annoying as it breaks every time >> anyone touches the kernel on one of this machines. >> >> Jeff, David, James: can you please make a decision of who takes this and >> then just do it? > > Ping? Ping indeed. Waiting as if HP is going to say "yes, we fucked that up. Go ahead with the patch." is silly. -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
