From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Dong Aisheng <dong.aisheng@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Thierry Reding <thierry.reding@avionic-design.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v7 2/2] mfd: syscon: Add non-DT support
Date: Wed, 13 Mar 2013 12:55:44 -0600 [thread overview]
Message-ID: <5140CBB0.3000204@wwwdotorg.org> (raw)
In-Reply-To: <1363200208.124789915@f299.mail.ru>
On 03/13/2013 12:43 PM, Alexander Shiyan wrote:
>> On 03/13/2013 11:34 AM, Alexander Shiyan wrote:
>>> This patch allow using syscon driver from the platform data, i.e.
>>> possibility using driver on systems without oftree support.
>>> For search syscon device from the client drivers,
>>> "syscon_regmap_lookup_by_pdevname" function was added.
>>
>> This patch also removes the driver's remove() function, which isn't
>> mentioned in the commit description.
>
> Driver is using resource managed functions, remove() is not necessary.
Ah right, I see that conversion was made in this patch. It seems like it
should be mentioned in the commit description, but it's probably not a
big deal unless there is some other reason to repost this.
next prev parent reply other threads:[~2013-03-13 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 17:34 [PATCH v7 1/2] mfd: syscon: Removed unneeded field "dev" from private driver structure Alexander Shiyan
2013-03-13 17:34 ` [PATCH v7 2/2] mfd: syscon: Add non-DT support Alexander Shiyan
2013-03-13 18:33 ` Stephen Warren
2013-03-13 18:43 ` Re[2]: " Alexander Shiyan
2013-03-13 18:55 ` Stephen Warren [this message]
2013-03-14 2:51 ` Dong Aisheng
2013-03-15 4:26 ` Re[2]: " Alexander Shiyan
2013-03-15 10:42 ` Arnd Bergmann
2013-03-16 6:20 ` Re[4]: " Alexander Shiyan
2013-04-05 15:58 ` [PATCH v7 1/2] mfd: syscon: Removed unneeded field "dev" from private driver structure Samuel Ortiz
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=5140CBB0.3000204@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dong.aisheng@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=shc_work@mail.ru \
--cc=thierry.reding@avionic-design.de \
/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