From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Only unregister platform devices allocated by the mfd core
Date: Fri, 9 Nov 2012 13:32:05 +0000 [thread overview]
Message-ID: <20121109133205.GF23807@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121108172300.GA21812@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
On Thu, Nov 08, 2012 at 05:23:00PM +0000, Charles Keepax wrote:
> +static struct device_type mfd_dev_type = {
> + .name = "MFD_DEVICE",
> +};
This seems non-idiomatic, other device types all have lower case names
(which are much more common in Unixish systems in general).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-11-09 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 17:23 [PATCH] mfd: Only unregister platform devices allocated by the mfd core Charles Keepax
2012-11-09 13:32 ` Mark Brown [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=20121109133205.GF23807@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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