public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@osdl.org>,
	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 22:20:16 -0800	[thread overview]
Message-ID: <20050304062016.GO5389@shell0.pdx.osdl.net> (raw)
In-Reply-To: <4227FC5C.60707@pobox.com>

* Jeff Garzik (jgarzik@pobox.com) wrote:
> Andrew Morton wrote:
> >Chris Wright <chrisw@osdl.org> wrote:
> >>Olof's patch is in the linux-release tree, so this brings up a point
> >>regarding merging.  If the quick fix is to be replaced by a better fix
> >>later (as in this case) there's some room for merge conflict.  Does this
> >>pose a problem for either -mm or Linus' tree?
> >
> >It depends who gets to Linus's tree first.  If linux-release merges first,
> >I just revert the temp fix while adding the real fix.  But the temp fix
> >should never have gone into Linus's tree in the first place.

Consider it first patch in fixup series ;-)

> >If I merge before linux-release, I guess Linus has some conflict resolving
> >to do when he pulls from linux-release.  That's OK for an obvious
> >two-liner, but would get out of control for more substantial things.
> >
> >Neither solution is acceptable, really.  I suspect the idea of pulling
> >linux-release into mainline won't work very well, and that making it a
> >backport tree would be more practical.
> 
> Maybe you're right, but I tend to think that "quick, get that fix out 
> immediately" fixes will appear before more substantial fixes.  That is 
> certainly the way things have worked up until now.
> 
> For the cases that we care about, putting that into linux-release and 
> then pulling would seem more appropriate.

Yes, and this case was on the border of a newly existing system.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2005-03-04  6:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 18:05 [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec 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 [this message]
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
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=20050304062016.GO5389@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