From: Jingoo Han <jg1.han@samsung.com>
To: 'David Miller' <davem@davemloft.net>
Cc: netdev@vger.kernel.org, pgynther@google.com,
'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: [PATCH 1/5] net: emac: use platform_{get,set}_drvdata()
Date: Wed, 04 Sep 2013 12:00:18 +0900 [thread overview]
Message-ID: <000901cea91a$e36f5050$aa4df0f0$%han@samsung.com> (raw)
In-Reply-To: <20130903.224003.792091851244921220.davem@davemloft.net>
On Wednesday, September 04, 2013 11:40 AM, David Miller wrote:
>
> From: Jingoo Han <jg1.han@samsung.com>
> Date: Mon, 02 Sep 2013 17:06:52 +0900
>
> > Use the wrapper functions for getting and setting the driver data
> > using platform_device instead of using dev_{get,set}_drvdata()
> > with &pdev->dev, so we can directly pass a struct platform_device.
> > This is a purely cosmetic change.
> >
> > Signed-off-by: Jingoo Han <jg1.han@samsung.com>
>
> All 5 patches applied.
>
> Please, in the future, provide an initial "[PATCH 00/nn] " posting for
> a series of patches, giving a top-level description of what is happening.
OK, I will provide an initial "[PATCH 00/nn]" posting.
Thank you for your suggestion. :-)
Best regards,
Jingoo Han
>
> This way I can include that commit message text in a merge commit and
> also I have an appropriate email to reply to if I just want to say
> that I applied everything in the series.
prev parent reply other threads:[~2013-09-04 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:06 [PATCH 1/5] net: emac: use platform_{get,set}_drvdata() Jingoo Han
2013-09-02 8:08 ` [PATCH 2/5] net: sunhme: " Jingoo Han
2013-09-02 8:10 ` [PATCH 3/5] net: mdio-octeon: " Jingoo Han
2013-09-02 8:11 ` [PATCH 4/5] net: tulip: use pci_{get,set}_drvdata() Jingoo Han
2013-09-02 8:12 ` [PATCH 5/5] net: sunhme: " Jingoo Han
2013-09-04 2:40 ` [PATCH 1/5] net: emac: use platform_{get,set}_drvdata() David Miller
2013-09-04 3:00 ` Jingoo Han [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='000901cea91a$e36f5050$aa4df0f0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pgynther@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).