From: Chris Wright <chrisw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Chris Wright <chrisw@osdl.org>,
jgarzik@pobox.com, olof@austin.ibm.com, paulus@samba.org,
rene@exactcode.de, torvalds@osdl.org,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec
Date: Thu, 3 Mar 2005 23:04:18 -0800 [thread overview]
Message-ID: <20050304070418.GQ5389@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050303225445.165f34da.akpm@osdl.org>
* Andrew Morton (akpm@osdl.org) wrote:
> Chris Wright <chrisw@osdl.org> wrote:
> >
> > > And it's a temp-fix - it'll be addressed by other means in 2.6.12.
> > >
> > > What do we do?
> >
> > IMO, we have to rely on Dmitry's judgement. Is it critical (i.e. broke
> > laptops how)? Can it be worked around with the i8042.noacpi boot param?
> > If so, I don't think it fits the bill as critical.
>
> Well. It was critical for 2.6.11, but it didn't make it :(
Ah, I see.
> So people whose keyboards don't work need to either update to 2.6.11.1 or
> add i8042.noacpi=1. <rekicks self>
>
> But it's just a for-instance.
And a good one to exercise the rules measuring how critical the patch
is. In this case, I don't think it is if workaround is good enough, but
could be convinced if Dmitry thinks otherwise.
Anyway, time to pack, sleep a few and catch a plane back west
later,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-03-04 7:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 18:05 Rene Rebe
2005-03-03 18:26 ` Jeff Garzik
2005-03-03 18:48 ` Greg KH
2005-03-03 18:59 ` Rene Rebe
2005-03-03 19:18 ` Greg KH
2005-03-03 19:48 ` Jeff Garzik
2005-03-03 20:07 ` Chris Wright
2005-03-03 20:32 ` Greg KH
2005-03-03 20:57 ` Jeff Garzik
2005-03-04 12:10 ` Francois Romieu
2005-03-03 22:30 ` Paul Mackerras
2005-03-03 22:45 ` Greg KH
2005-03-03 23:05 ` Dave Jones
2005-03-03 22:55 ` Olof Johansson
2005-03-03 23:14 ` Greg KH
2005-03-04 1:59 ` Andrew Morton
2005-03-04 2:24 ` Olof Johansson
2005-03-04 5:54 ` Chris Wright
2005-03-04 6:06 ` Jeff Garzik
2005-03-04 6:17 ` Andrew Morton
2005-03-04 6:33 ` Jeff Garzik
2005-03-04 6:06 ` Andrew Morton
2005-03-04 6:12 ` Jeff Garzik
2005-03-04 6:20 ` Andrew Morton
2005-03-04 6:20 ` Chris Wright
2005-03-04 6:23 ` Andrew Morton
2005-03-04 6:47 ` Chris Wright
2005-03-04 6:54 ` Andrew Morton
2005-03-04 7:04 ` Chris Wright [this message]
2005-03-04 7:05 ` Jeff Garzik
2005-03-04 7:12 ` Andrew Morton
2005-03-04 7:14 ` Jeff Garzik
2005-03-04 16:27 ` Greg KH
2005-03-04 18:38 ` Linus Torvalds
2005-03-04 18:41 ` Greg KH
2005-03-06 23:06 ` Alan Cox
2005-03-07 18:03 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050304070418.GQ5389@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@austin.ibm.com \
--cc=paulus@samba.org \
--cc=rene@exactcode.de \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome