From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-mediatek@lists.infradead.org,
John Crispin <blogic@openwrt.org>,
linux-arm-kernel@lists.infradead.org,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: [PATCH 0/2] regulator: mt6397: Add platform and OF tables and fix module autoload
Date: Mon, 25 Jan 2016 11:37:14 -0300 [thread overview]
Message-ID: <1453732637-20415-1-git-send-email-javier@osg.samsung.com> (raw)
Hello Mark,
This small series add missing platform device and OF tables to the mt6397
regulator driver. I noticed these when reviewing a new regulator driver
that was posted since the submitted driver had the same issues [0].
The patches were just built tested so testing on an actual HW will be highly
appreciated.
[0]: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1058808.html
Best regards,
Javier
Javier Martinez Canillas (2):
regulator: mt6397: Add platform device ID table
regulator: mt6397: Add OF match table
drivers/regulator/mt6397-regulator.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
--
2.5.0
next reply other threads:[~2016-01-25 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 14:37 Javier Martinez Canillas [this message]
2016-01-25 14:37 ` [PATCH 1/2] regulator: mt6397: Add platform device ID table Javier Martinez Canillas
2016-01-27 18:38 ` Applied "regulator: mt6397: Add platform device ID table" to the regulator tree Mark Brown
2016-01-25 14:37 ` [PATCH 2/2] regulator: mt6397: Add OF match table Javier Martinez Canillas
2016-01-27 18:38 ` Applied "regulator: mt6397: Add OF match table" to the regulator tree Mark Brown
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=1453732637-20415-1-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=blogic@openwrt.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@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
all inboxes | Powered by JetHome®