All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Gustavo Barbieri <barbieri@gmail.com>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	debian-kernel@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: rs/6000 e30 + 240 (doral) support
Date: Thu, 29 Jul 2004 17:18:13 +0200	[thread overview]
Message-ID: <20040729151813.GB13987@pegasos> (raw)
In-Reply-To: <9ef20ef304072907243f820e04@mail.gmail.com>


On Thu, Jul 29, 2004 at 11:24:35AM -0300, Gustavo Barbieri wrote:
> On Thu, 29 Jul 2004 16:16:31 +0200, Christoph Hellwig <hch@lst.de> wrote:
> > On Thu, Jul 29, 2004 at 11:04:48AM -0300, Gustavo Barbieri wrote:
> > > > Most doesn't look too bad to me, but it's a lot of patches.  I vaguely
> > > > remember they were discussed on linuxppc-dev, so we should check the
> > > > comments over there.
> > >
> > > A lot of patches? Well, there is a lot of "code"... it's not really
> > > code, but just structure definitions... actually the patche touches
> > > the real code at few points, one it's just a null pointer checking,
> > > other are added cases to the switch statement so it can handle those
> > > boards, so I really can't a problem there.
> > >
> > > I already sent an email to linuxppc-dev in the past, but no replies:
> > >
> > > http://lists.linuxppc.org/linuxppc-dev/200407/msg00085.html
> >
> > Ah sorry, I confused it with Len's big IBM prep patchkit.  Except for a
> > tiny style issue this patch is fine with me.
>
> What style issue?
>
>
> > Any upstream comments as I'd hate to carry along a patch like that in
> > the Debian patchkit while we'd probably want it in Sarge.
> >
> > Gustavo, if we apply this patch you'll have to sign up for d-i testing
> > on prep, though ;-)
>
> Ok, I test... actually I'm using sarge on that machine.
>
> But I need to test it soon, as this machine may go away in few weeks.

Well, since sarge d-i will probably be released before you lose that machine,
it should be no problem. We first need to rebuild a kernel though.

Christoph, do this and other patches warrant a kernel-source 2.6.7-4 upload,
or is it better to keep it in the powerpc patches for now ?

Friendly;

Sven Luther

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-29 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9ef20ef304071613494a0f0af9@mail.gmail.com>
     [not found] ` <20040717014441.GA13447@pegasos>
     [not found]   ` <20040729135130.GE19197@lst.de>
     [not found]     ` <9ef20ef3040729070439f6d8c1@mail.gmail.com>
2004-07-29 14:16       ` rs/6000 e30 + 240 (doral) support Christoph Hellwig
2004-07-29 14:24         ` Gustavo Barbieri
2004-07-29 15:18           ` Sven Luther [this message]
2004-07-29 15:34             ` Christoph Hellwig
2004-07-29 15:53             ` Gustavo Barbieri
2004-07-29 15:01         ` Leigh Brown
2004-07-29 15:37           ` Gustavo Barbieri
2004-07-29 21:14             ` Leigh Brown
2004-07-13 21:24 Gustavo Barbieri

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=20040729151813.GB13987@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=barbieri@gmail.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.