From: Wolfram Sang <wsa@the-dreams.de>
To: James Ralston <james.d.ralston@intel.com>
Cc: linux-doc@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
Seth Heasley <seth.heasley@intel.com>
Subject: Re: [PATCH 3/4] i2c-i801: Add Device IDs for Intel Wildcat Point-LP PCH
Date: Thu, 14 Nov 2013 18:29:01 +0100 [thread overview]
Message-ID: <20131114172901.GE11022@katana> (raw)
In-Reply-To: <1383586188-4717-1-git-send-email-james.d.ralston@intel.com>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
On Mon, Nov 04, 2013 at 09:29:48AM -0800, James Ralston wrote:
> This patch adds the SMBus Device IDs for the Intel Wildcat Point-LP PCH.
>
> Signed-off-by: James Ralston <james.d.ralston@intel.com>
Applied to for-next, thanks! Please ensure that the introductory message
also goes to the relevant mailing lists.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-11-14 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 17:29 [PATCH 3/4] i2c-i801: Add Device IDs for Intel Wildcat Point-LP PCH James Ralston
2013-11-14 17:29 ` Wolfram Sang [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=20131114172901.GE11022@katana \
--to=wsa@the-dreams.de \
--cc=james.d.ralston@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@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;
as well as URLs for NNTP newsgroup(s).