From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Miles Lane <miles.lane@comcast.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc-2.5 (mvista rsync) -- drivers/ide/ppc/pmac.c:1843: error: request for member `queue_head' in something not a structure or union
Date: 10 Aug 2003 22:55:25 +0200 [thread overview]
Message-ID: <1060548925.599.42.camel@gaston> (raw)
In-Reply-To: <200308101351.01114.miles.lane@comcast.net>
On Sun, 2003-08-10 at 22:51, Miles Lane wrote:
> On Sun August 10 2003 1:38 pm, Benjamin Herrenschmidt wrote:
> > On Sun, 2003-08-10 at 17:51, Miles Lane wrote:
> > > CC drivers/ide/ppc/pmac.o
> > > drivers/ide/ppc/pmac.c: In function `idepmac_wake_device':
> > > drivers/ide/ppc/pmac.c:1843: error: request for member `queue_head' in
> > > something not a structure or union
> > > drivers/ide/ppc/pmac.c: In function `idepmac_wake_drive':
> > > drivers/ide/ppc/pmac.c:1927: error: request for member `queue_head' in
> > > something not a structure or union
> >
> > I sent an updated version of this driver to linus today
>
> When you send patches to Linus to fix problems that show up in
> the linuxppc-2.5 tree, you don't also apply the patch directly to
> the linuxppc-2.5 tree? If you and Paul use BK, couldn't you have
> Paul pull the changeset? Is our current process the most efficient
> we could use?
Right now, I'm sending massive PowerMac driver updates directly
to Linus. Typically, all of this is available from my linuxppc-2.5-benh
tree, though I don't really recommend for non-hackers to use that.
> I am curious, why do you and Paul not use a system more like Russell's
> (changes move into Linus' tree as soon as they are fairly well tested
> and he maintains the ARM patches in
I'm trying to completely avoid having a "ppc" or "powermac" tree with
2.6, at least once all the "pending" bits from mine have been in Linus.
I want to keep as close as Linus tree as I can, not reproduce what I did
for 2.4 where I had megabytes of diffs piling up.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-10 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 15:51 linuxppc-2.5 (mvista rsync) -- drivers/ide/ppc/pmac.c:1843: error: request for member `queue_head' in something not a structure or union Miles Lane
2003-08-10 15:57 ` Miles Lane
2003-08-10 20:38 ` Benjamin Herrenschmidt
2003-08-10 20:51 ` Miles Lane
2003-08-10 20:55 ` Benjamin Herrenschmidt [this message]
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=1060548925.599.42.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=miles.lane@comcast.net \
/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.