From: Jin Dongming <jin.dongming@np.css.fujitsu.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andi Kleen <andi@firstfloor.org>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
ACPI <linux-acpi@vger.kernel.org>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] [Patch-next] ACPI, APEI, HEST Fix the unsuitable usage of platform_data.
Date: Tue, 17 Aug 2010 18:18:31 +0900 [thread overview]
Message-ID: <4C6A53E7.3090301@np.css.fujitsu.com> (raw)
In-Reply-To: <1282018698.2744.1508.camel@yhuang-dev>
(2010/08/17 13:18), Huang Ying wrote:
> On Tue, 2010-08-17 at 11:00 +0800, Jin Dongming wrote:
>>> Why not use platform_device_add_data?
>> Here what should be done is to transport the pointer of hest_hdr to platform_data,
>> so I think that it could be done successfully by allocating 8byte of memory.
>> If the platform_device_add_data() is used, the more memory will be allocated.
>>
>> So I think this method is better than using platform_device_add_data().
>
> You can specify allocation size for platform_device_add_data(), so no
> more memory will be allocated.
>
> Best Regards,
> Huang Ying
I am sorry for replying late.
I will modify my patch and resend it again.
Best Regards,
Jin Dongming
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~2010-08-17 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 0:58 [PATCH 4/4] [Patch-next] ACPI, APEI, HEST Fix the unsuitable usage of platform_data Jin Dongming
2010-08-17 1:39 ` Huang Ying
2010-08-17 3:00 ` Jin Dongming
2010-08-17 4:18 ` Huang Ying
2010-08-17 9:18 ` Jin Dongming [this message]
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=4C6A53E7.3090301@np.css.fujitsu.com \
--to=jin.dongming@np.css.fujitsu.com \
--cc=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=sfr@canb.auug.org.au \
--cc=ying.huang@intel.com \
/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.