From: Daniel Walker <dwalker@mvista.com>
To: Haavard Skinnemoen <hskinnemoen@gmail.com>
Cc: linux-kernel@vger.kernel.org, Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [PATCH 04/12] clocksource: avr32 initialize list value
Date: Tue, 23 Jan 2007 05:02:49 -0800 [thread overview]
Message-ID: <1169557370.19471.20.camel@imap.mvista.com> (raw)
In-Reply-To: <1defaf580701230442p3f0d6b66ue7d67a88abf5a66a@mail.gmail.com>
On Tue, 2007-01-23 at 13:42 +0100, Haavard Skinnemoen wrote:
> On 1/23/07, Daniel Walker <dwalker@mvista.com> wrote:
> > Update arch/avre32/ with list initialization.
> >
> > Signed-Off-By: Daniel Walker <dwalker@mvista.com>
>
> Looks good to me, although I suppose it wouldn't hurt to include
> <linux/list.h> as well since there seems to be an ongoing effort to
> reduce the number of files that are included implicitly through other
> headers. Might save us from some trouble later.
It shouldn't be outright implicit since it's included in clocksource.h .
That has to be included before you can create a clocksource. I could see
adding list.h if it wasn't clear which include was bringing it in.
> I've closed your support request, so you shouldn't expect a reply from
> avr32@atmel.com (I was going to reply through the support system, but
> I couldn't figure out how to prevent it from top-quoting.) Probably
> best if you send patches directly to me at hskinnemoen@atmel.com, but
> the support address is a nice fallback if I'm unable to respond for
> some reason.
I got that address from the maintainers file,
AVR32 ARCHITECTURE
P: Atmel AVR32 Support Team
M: avr32@atmel.com
P: Haavard Skinnemoen
M: hskinnemoen@atmel.com
W: http://www.atmel.com/products/AVR32/
W: http://avr32linux.org/
W: http://avrfreaks.net/
S: Supported
I just picked the top address .. If it makes sense you might want to
consider dropping that address from the maintainers file. It seems a
little formal for submitting patches. In the future I'll send them to
you.
Daniel
next prev parent reply other threads:[~2007-01-23 13:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 5:52 [PATCH 00/12] clocksource/timekeeping cleanup Daniel Walker
2007-01-23 5:52 ` [PATCH 01/12] timekeeping: create kernel/time/timekeeping.c Daniel Walker
2007-01-23 5:52 ` [PATCH 02/12] clocksource: rating sorted list Daniel Walker
2007-01-23 5:52 ` [PATCH 03/12] clocksource: arm initialize list value Daniel Walker
2007-01-23 5:52 ` [PATCH 04/12] clocksource: avr32 " Daniel Walker
2007-01-23 12:42 ` Haavard Skinnemoen
2007-01-23 13:02 ` Daniel Walker [this message]
2007-01-23 13:44 ` Haavard Skinnemoen
2007-01-23 5:53 ` [PATCH 05/12] clocksource: mips " Daniel Walker
2007-01-23 5:53 ` [PATCH 06/12] clocksource: i386 " Daniel Walker
2007-01-23 5:53 ` [PATCH 07/12] clocksource: x86_64 " Daniel Walker
2007-01-23 5:53 ` [PATCH 08/12] clocksource: driver " Daniel Walker
2007-01-23 5:53 ` [PATCH 09/12] clocksource: " Daniel Walker
2007-01-23 5:53 ` [PATCH 10/12] clocksource: add block notifier Daniel Walker
2007-01-23 5:53 ` [PATCH 11/12] clocksource: remove update_callback Daniel Walker
2007-01-23 5:53 ` [PATCH 12/12] clocksource: atomic signals Daniel Walker
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=1169557370.19471.20.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=hskinnemoen@atmel.com \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®