linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Seth Heasley
	<seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] i2c-i801: Move device ID definitions to driver
Date: Mon, 25 Apr 2011 11:45:20 -0700	[thread overview]
Message-ID: <20110425114520.741ff0ff@jbarnes-desktop> (raw)
In-Reply-To: <20110423095808.6f6ee01d-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>

On Sat, 23 Apr 2011 09:58:08 +0200
Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:

> Move the SMBus device ID definitions of recent devices from pci_ids.h
> to the i2c-i801.c driver file. They don't have to be shared, as they
> are clearly identified and only used in this driver. In the future,
> such IDs will go to i2c-i801 directly. This will make adding support
> for new devices much faster and easier, as it will avoid cross-
> subsystem patch sets and merge conflicts.
> 
> Signed-off-by: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
> Cc: Seth Heasley <seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Cc: Jesse Barnes <jbarnes-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org>
> ---

Acked-by: Jesse Barnes <jbarnes-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org>

You can just push this through your tree.  Thanks Jean.

-- 
Jesse Barnes, Intel Open Source Technology Center

      parent reply	other threads:[~2011-04-25 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23  7:58 [PATCH] i2c-i801: Move device ID definitions to driver Jean Delvare
     [not found] ` <20110423095808.6f6ee01d-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-25 18:45   ` Jesse Barnes [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=20110425114520.741ff0ff@jbarnes-desktop \
    --to=jbarnes-y1mf5jbuw70benjcbmcuuq@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).