From: Miles Lane <miles.lane@comcast•net>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
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: Sun, 10 Aug 2003 13:51:01 -0700 [thread overview]
Message-ID: <200308101351.01114.miles.lane@comcast.net> (raw)
In-Reply-To: <1060547919.599.34.camel@gaston>
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?
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
http://www.kernel.org/pub/linux/kernel/people/rmk/arm/v2.5/)?
Thanks,
Miles
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-10 20:51 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 [this message]
2003-08-10 20:55 ` Benjamin Herrenschmidt
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=200308101351.01114.miles.lane@comcast.net \
--to=miles.lane@comcast$(echo .)net \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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