linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: lm-sensors@lm-sensors.org, Jean Delvare <khali@linux-fr.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (sht15) remove multiple driver registration
Date: Fri, 31 Aug 2012 09:06:04 -0700	[thread overview]
Message-ID: <20120831160604.GB5756@roeck-us.net> (raw)
In-Reply-To: <1346377579-24849-1-git-send-email-vivien.didelot@savoirfairelinux.com>

On Thu, Aug 30, 2012 at 09:46:19PM -0400, Vivien Didelot wrote:
> Declare an array of platform_device_id, instead of registering a driver
> for each supported chip. This makes the code cleaner.
> Also add a module description.
> 
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>

Applied to -next.

Thanks,
Guenter

      reply	other threads:[~2012-08-31 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  1:46 Vivien Didelot
2012-08-31 16:06 ` Guenter Roeck [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=20120831160604.GB5756@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=vivien.didelot@savoirfairelinux.com \
    --subject='Re: [PATCH] hwmon: (sht15) remove multiple driver registration' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).