From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] RFC: make struct platform_driver.id_table const
Date: Wed, 27 Jan 2010 17:11:38 -0800 [thread overview]
Message-ID: <20100128011135.GA24068@kroah.com> (raw)
In-Reply-To: <f17812d71001260054g57b282c4n90977cc76d521f89@mail.gmail.com>
On Tue, Jan 26, 2010 at 04:54:13PM +0800, Eric Miao wrote:
> 2010/1/26 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
> > Greg,
> >
> > On Tue, Jan 26, 2010 at 02:01:15PM +0800, Eric Miao wrote:
> >> I seems to remember a similar patch sent to GregKH weeks ago and
> >> should be sitting somewhere but this one looks to be more complete.
> > Yes, it's
> > ? ? ? ?gregkh-2.6/gregkh-05-driver-core/driver-core-make-platform_device_id-table-const.patch
> >
> > Below you can find the current state with all Acks it has got until now.
> > (Eric: I considered your mail as Ack, too. ?OK?)
>
> OK.
>
> > As I don't know how to change the log message with an incremental patch
> > you have to tell me if you prefer this way.
>
> Greg?
I took out the chunk that came in the previous patch, and applied it.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Vikram Dhillon" <opensolarisdev@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Eric Miao" <eric.miao@marvell.com>,
linux-kernel@vger.kernel.org, "Ben Dooks" <ben-linux@fluff.org>
Subject: Re: [PATCH] RFC: make struct platform_driver.id_table const
Date: Wed, 27 Jan 2010 17:11:38 -0800 [thread overview]
Message-ID: <20100128011135.GA24068@kroah.com> (raw)
In-Reply-To: <f17812d71001260054g57b282c4n90977cc76d521f89@mail.gmail.com>
On Tue, Jan 26, 2010 at 04:54:13PM +0800, Eric Miao wrote:
> 2010/1/26 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> > Greg,
> >
> > On Tue, Jan 26, 2010 at 02:01:15PM +0800, Eric Miao wrote:
> >> I seems to remember a similar patch sent to GregKH weeks ago and
> >> should be sitting somewhere but this one looks to be more complete.
> > Yes, it's
> > gregkh-2.6/gregkh-05-driver-core/driver-core-make-platform_device_id-table-const.patch
> >
> > Below you can find the current state with all Acks it has got until now.
> > (Eric: I considered your mail as Ack, too. OK?)
>
> OK.
>
> > As I don't know how to change the log message with an incremental patch
> > you have to tell me if you prefer this way.
>
> Greg?
I took out the chunk that came in the previous patch, and applied it.
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-28 1:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 17:03 [PATCH] RFC: make struct platform_driver.id_table const Uwe Kleine-König
2010-01-22 17:03 ` Uwe Kleine-König
2010-01-25 1:34 ` Ben Dooks
2010-01-25 1:34 ` Ben Dooks
2010-01-25 2:15 ` Vikram Dhillon
2010-01-25 2:15 ` Vikram Dhillon
2010-01-25 7:42 ` Uwe Kleine-König
2010-01-25 7:42 ` Uwe Kleine-König
2010-01-25 21:12 ` Vikram Dhillon
2010-01-25 21:12 ` Vikram Dhillon
2010-01-26 6:01 ` Eric Miao
2010-01-26 6:01 ` Eric Miao
2010-01-26 8:35 ` Uwe Kleine-König
2010-01-26 8:35 ` Uwe Kleine-König
2010-01-26 8:54 ` Eric Miao
2010-01-26 8:54 ` Eric Miao
2010-01-28 1:11 ` Greg KH [this message]
2010-01-28 1:11 ` Greg KH
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=20100128011135.GA24068@kroah.com \
--to=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.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.