From: "John Lenz" <lenz@cs.wisc.edu>
To: "Richard Purdie" <rpurdie@rpsys.net>
Cc: "Russell King" <rmk+lkml@arm.linux.org.uk>,
"Pavel Machek" <pavel@suse.cz>,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] Fix compilation in locomo.c
Date: Thu, 8 Sep 2005 18:31:03 -0500 (CDT) [thread overview]
Message-ID: <41299.192.168.0.13.1126222263.squirrel@192.168.0.2> (raw)
In-Reply-To: <1126015886.8338.147.camel@localhost.localdomain>
On Tue, September 6, 2005 9:11 am, Richard Purdie said:
> On Sun, 2005-09-04 at 11:33 +0100, Russell King wrote:
>> On Tue, Jul 26, 2005 at 08:30:43AM +0200, Pavel Machek wrote:
>> > Do not access children in struct device directly, use
>> > device_for_each_child helper instead. It fixes compilation.
>> >
>> > Signed-off-by: Pavel Machek <pavel@suse.cz>
>>
>> Given up waiting for John/Richard to okay this, applied anyway.
>
> You did get a response from me on 20/8/05 which said:
>
> "Locomo is outside my area of expertise and its not present on the
> devices I use/maintain, hence this is something John would have the
> definitive opinion on. The patch looks sane to me though."
>
> I suspect John is between email addresses at the moment. Hopefully he'll
> be back with us soon.
Yeah... I'm now back but haven't yet had a chance to look at any patches
or anything that has been floating around. Next week I will look closer
at these patches (even if they have already been applied).
John
prev parent reply other threads:[~2005-09-08 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 6:30 Pavel Machek
2005-09-04 10:33 ` Russell King
2005-09-06 14:11 ` Richard Purdie
2005-09-08 23:31 ` John Lenz [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=41299.192.168.0.13.1126222263.squirrel@192.168.0.2 \
--to=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rpurdie@rpsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®