From: Arnd Bergmann <arnd@arndb.de>
To: Ryan Mallon <rmallon@gmail.com>
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
gregkh@linuxfoundation.org
Subject: Re: [PATCH 3/3] misc: ep93xx_pwm.c: fix section mismatch and use module_platform_driver
Date: Mon, 25 Mar 2013 21:49:16 +0000 [thread overview]
Message-ID: <201303252149.16960.arnd@arndb.de> (raw)
In-Reply-To: <5145095D.3010304@gmail.com>
On Sunday 17 March 2013, Ryan Mallon wrote:
> On 17/03/13 01:57, Arnd Bergmann wrote:
>
> > On Saturday 16 March 2013, H Hartley Sweeten wrote:
> >> Remove the __init tags from the ep93xx_pwm_probe() and
> >> ep93xx_pwm_remove() functions to fix the section mismatch
> >> warnings.
> >>
> >> Use module_platform_driver() to remove the init/exit boilerplate.
> >>
> >> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> >> Cc: Ryan Mallon <rmallon@gmail.com>
> >> Cc: Arnd Bergmann <arnd@arndb.de>
> >> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
>
>
> For the whole series:
>
> Acked-by: Ryan Mallon <rmallon@gmail.com>
>
> Not sure if I should take these in my tree, or if they should be
> handled by the respective subsystem maintainers. Arnd?
Doesn't matter much, as there are no dependencies. The default would
be to ask the subsystem maintainers to put them into their trees.
If that doesn't happen for some reason, I can take them through the
arm-soc tree as a fallback.
Arnd
next prev parent reply other threads:[~2013-03-25 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 1:07 [PATCH 3/3] misc: ep93xx_pwm.c: fix section mismatch and use module_platform_driver H Hartley Sweeten
2013-03-16 14:57 ` Arnd Bergmann
2013-03-17 0:07 ` Ryan Mallon
2013-03-25 21:49 ` Arnd Bergmann [this message]
2013-03-25 20:17 ` 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=201303252149.16960.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmallon@gmail.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