From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel@pengutronix.de, Greg Kroah-Hartman <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] RFC: introduce typechecking to platform_{get,set}_drvdata
Date: Wed, 16 Feb 2011 22:59:32 +0100 [thread overview]
Message-ID: <4D5C48C4.1090403@pengutronix.de> (raw)
In-Reply-To: <20110216135547.8940e19d.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On 02/16/2011 10:55 PM, Andrew Morton wrote:
> On Wed, 16 Feb 2011 22:49:52 +0100
> Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>
>> From: Marc Kleine-Budde <mkl@pengutronix.de>
>> To: kernel@pengutronix.de
>> Cc: Greg Kroah-Hartman <gregkh@suse.de>, Andrew Morton <akpm@linux-foundation.org>
>
> No mailing list was cc'ed.
just noticed, sorry :(
>> Subject: [PATCH 0/2] RFC: introduce typechecking to platform_{get,set}_drvdata
>> Date: Wed, 16 Feb 2011 22:49:52 +0100
>> X-Mailer: git-send-email 1.7.2.3
>>
>> Hello,
>>
>> just found a mis-user of platform_set_drvdata(), so introduce typechecking
>> to these macro definitions.
>
> ick.
>
>> An alternative would be to make them static inline
>> functions.
>
> A vastly preferable alternative! How's about doing that?
Sure...wait for "v2"
regards, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next parent reply other threads:[~2011-02-16 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1297892994-30801-1-git-send-email-mkl@pengutronix.de>
[not found] ` <20110216135547.8940e19d.akpm@linux-foundation.org>
2011-02-16 21:59 ` Marc Kleine-Budde [this message]
2011-02-16 21:55 [PATCH 0/2] RFC: introduce typechecking to platform_{get,set}_drvdata Marc Kleine-Budde
2011-02-16 22:02 ` 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=4D5C48C4.1090403@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=kernel@pengutronix.de \
--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