All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: tglx@linutronix.de, johnstul@us.ibm.com, mingo@elte.hu,
	LKML <linux-kernel@vger.kernel.org>,
	heiko.carstens@de.ibm.com
Subject: Re: + clocksource-driver-initialize-list-value.patch added to -mm tree
Date: Wed, 04 Apr 2007 13:10:25 -0700	[thread overview]
Message-ID: <1175717425.15973.61.camel@imap.mvista.com> (raw)
In-Reply-To: <20070404125853.1cf9b7b7.akpm@linux-foundation.org>

On Wed, 2007-04-04 at 12:58 -0700, Andrew Morton wrote:
> On Wed, 04 Apr 2007 09:38:32 -0700
> Daniel Walker <dwalker@mvista.com> wrote:
> 
> > On Sun, 2007-04-01 at 10:43 +0200, Thomas Gleixner wrote:
> > > On Sat, 2007-03-31 at 22:23 -0700, akpm@linux-foundation.org wrote:
> > > > The patch titled
> > > >      clocksource: driver initialize list value
> > > > has been added to the -mm tree.  Its filename is
> > > >      clocksource-driver-initialize-list-value.patch
> > > > 
> > > > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> > > > 
> > > > See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> > > > out what to do about this
> > > > 
> > > > ------------------------------------------------------
> > > > Subject: clocksource: driver initialize list value
> > > > From: Daniel Walker <dwalker@mvista.com>
> > > > 
> > > > Update drivers/clocksource/ with list initialization.
> > > 
> > > As others pointed out already, can we please have some usefull
> > > description why this change is necessary ? i.e. that it is a preparatory
> > > patch to simplify the clocksource registration logic.
> > > 
> > > 	tglx
> > 
> > I was planning to do it after Andrew release the next -mm then use same
> > patch names he has and just submit to him.. I'm not sure what the
> > easiest method is, and I'd rather like to avoid re-submitting to LKML ..
> 
> Please just send the updated text.  Telling me the name of the patch
> into which it is to be pasted is appreciated.

The following text,

---
The struct clocksource .list field is now required to be initialized
before calling clocksource_register().

This is a prerequisite for simplifying the clocksource
registration process.
---

Goes into ,

clocksource-arm-initialize-list-value.patch
clocksource-avr32-initialize-list-value.patch
clocksource-driver-initialize-list-value.patch
clocksource-i386-initialize-list-value.patch
clocksource-mips-initialize-list-value.patch
clocksource-parisc-initialize-list-value.patch
clocksource-s390-initialize-list-value.patch
clocksource-x86_64-initialize-list-value.patch

The patch names are from 2.6.21-rc5-mm4. Heiko, Thomas do either of you
have any comments on the text being added?

Daniel


  reply	other threads:[~2007-04-04 20:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200704010523.l315NXJP004063@shell0.pdx.osdl.net>
2007-04-01  8:43 ` + clocksource-driver-initialize-list-value.patch added to -mm tree Thomas Gleixner
2007-04-04 16:38   ` Daniel Walker
2007-04-04 19:58     ` Andrew Morton
2007-04-04 20:10       ` Daniel Walker [this message]
2007-04-04 20:36         ` Ingo Molnar
2007-04-04 20:44           ` Daniel Walker
2007-04-04 21:15             ` Ingo Molnar
2007-04-04 21:30               ` Daniel Walker
2007-04-04 21:34                 ` Ingo Molnar
2007-04-04 21:59                   ` Daniel Walker
2007-04-04 23:48                     ` Jeremy Fitzhardinge
2007-04-05  0:00                       ` Daniel Walker
2007-04-05  0:20                         ` Jeremy Fitzhardinge
2007-04-05  0:34                           ` Daniel Walker
2007-04-05  6:02                             ` Thomas Gleixner
2007-04-05  7:51                             ` Ingo Molnar
2007-04-05 11:35                               ` Daniel Walker
2007-04-04 20:48           ` Andrew Morton
2007-04-04 21:47             ` Thomas Gleixner

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=1175717425.15973.61.camel@imap.mvista.com \
    --to=dwalker@mvista.com \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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.