From: Mark Brown <broonie@kernel.org>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
David Dajun Chen <david.chen@diasemi.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1] DA9210 driver files
Date: Mon, 15 Jul 2013 17:57:35 +0100 [thread overview]
Message-ID: <20130715165735.GU11538@sirena.org.uk> (raw)
In-Reply-To: <201307151518.r6FFIve6031479@swsrvapps-01.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
On Mon, Jul 15, 2013 at 03:06:59PM +0100, Steve Twiss wrote:
> From: Steve Twiss <stwiss.opensource@diasemi.com>
>
> This patch describes the regulator driver for the DA9210 Multi-phase Buck
> from Dialog Semiconductor Ltd. It has been made aginst kernel version
> linux-next next-20130715
To repeat *again* you should submit patches in the format covered in
SubmittingPatches. This includes things like the commit message, if
your commit message doesn't look like other commit messages for the code
you're changing that's an issue.
> +struct da9210 {
> + struct device *dev;
This is never used as far as I can tell.
> +MODULE_ALIAS("platform: da9210");
This is for a platform device but this is an I2C device so would never
match. Also for a platform device the string should have no space in
it.
Otherwise this looks OK, though it'd be better to fill in the register
map information more (listing the valid registers for example).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-15 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 14:06 Steve Twiss
2013-07-15 16:57 ` Mark Brown [this message]
2013-08-06 13:09 ` Steve Twiss
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=20130715165735.GU11538@sirena.org.uk \
--to=broonie@kernel.org \
--cc=david.chen@diasemi.com \
--cc=g.liakhovetski@gmx.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stwiss.opensource@diasemi.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®