From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
johnstul@us.ibm.com
Subject: Re: [PATCH 8/9] clocksource: s390 initialize list value
Date: Fri, 30 Mar 2007 21:36:38 +0200 [thread overview]
Message-ID: <20070330193638.GC13240@osiris.ibm.com> (raw)
In-Reply-To: <1175282358.12252.179.camel@imap.mvista.com>
On Fri, Mar 30, 2007 at 12:19:18PM -0700, Daniel Walker wrote:
> On Fri, 2007-03-30 at 21:09 +0200, Heiko Carstens wrote:
> > On Fri, Mar 30, 2007 at 11:45:49AM -0700, Daniel Walker wrote:
> > > Update arch/s390 with list initialization.
> > >
> > > Signed-Off-By: Daniel Walker <dwalker@mvista.com>
[...]
> > Why? This doesn't fix anything...
>
> It's needed for patch 9/9 in the series.
Then maybe your patch description should reflect that?
If this gets merged as a seperate patch and somebody checks the git
history of arch/s390 and sees this patch... how could he know what
this is good for?
Does it fix a bug? Needed by any feature? Or...?
next prev parent reply other threads:[~2007-03-30 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 18:45 [PATCH 1/9] clocksource: arm initialize list value Daniel Walker
2007-03-30 18:45 ` [PATCH 2/9] clocksource: parisc " Daniel Walker
2007-03-30 18:45 ` [PATCH 3/9] clocksource: avr32 " Daniel Walker
2007-03-30 18:45 ` [PATCH 4/9] clocksource: mips " Daniel Walker
2007-03-30 18:45 ` [PATCH 5/9] clocksource: i386 " Daniel Walker
2007-03-30 18:45 ` [PATCH 6/9] clocksource: x86_64 " Daniel Walker
2007-03-30 18:45 ` [PATCH 7/9] clocksource: driver " Daniel Walker
2007-03-30 18:45 ` [PATCH 8/9] clocksource: s390 " Daniel Walker
2007-03-30 19:09 ` Heiko Carstens
2007-03-30 19:19 ` Daniel Walker
2007-03-30 19:36 ` Heiko Carstens [this message]
2007-03-30 18:45 ` [PATCH 9/9] clocksource: refactor duplicate registration checking Daniel Walker
2007-03-31 1:59 ` James Morris
2007-03-31 2:47 ` 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=20070330193638.GC13240@osiris.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.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 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.