From: Benson Leung <bleung@chromium.org>
To: wsa@the-dreams.de, mika.westerberg@linux.intel.com,
khali@linux-fr.org, andriy.shevchenko@linux.intel.com,
jacmet@sunsite.dk, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: dlaurie@chromium.org, bleung@chromium.org
Subject: [PATCH 0/2] i2c-designware-pci: Add Haswell ULT device support
Date: Sun, 20 Oct 2013 20:26:48 -0700 [thread overview]
Message-ID: <1382326010-4554-1-git-send-email-bleung@chromium.org> (raw)
Add the Haswell ULT device IDs for i2c-designware-pci. These are used,
for example, in Haswell generation Chromebooks, the HP Chromebook 14
and the Acer C720.
[PATCH 1/2] i2c-designware-pci: Add Haswell ULT device IDs
[PATCH 2/2] i2c-designware-pci: Index Haswell ULT bus names from 0
next reply other threads:[~2013-10-21 3:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 3:26 Benson Leung [this message]
2013-10-21 3:26 ` [PATCH 1/2] i2c-designware-pci: Add Haswell ULT device IDs Benson Leung
2013-10-21 6:53 ` Mika Westerberg
2013-10-21 14:23 ` Benson Leung
2013-10-21 3:26 ` [PATCH 2/2] i2c-designware-pci: Index Haswell ULT bus names from 0 Benson Leung
2013-10-21 6:58 ` Mika Westerberg
2013-10-21 14:20 ` Benson Leung
2013-10-21 16:12 ` Mika Westerberg
2013-11-14 18:05 ` Wolfram Sang
2013-11-20 2:14 ` Benson Leung
2013-11-26 13:09 ` Wolfram Sang
2014-01-03 15:52 ` Wolfram Sang
2014-01-10 0:12 ` Benson Leung
2014-01-10 7:59 ` Jean Delvare
2014-01-16 19:51 ` Wolfram Sang
2014-01-16 20:14 ` Benson Leung
2013-10-21 15:05 ` [PATCH v2 0/2] i2c-designware-pci: Add Haswell ULT device support Benson Leung
2013-10-21 15:05 ` [PATCH v2 1/2] i2c-designware-pci: Add Haswell ULT device IDs Benson Leung
2013-10-21 15:05 ` [PATCH v2 2/2] i2c-designware-pci: Index Haswell ULT bus names from 0 Benson Leung
2013-10-21 16:14 ` [PATCH v2 0/2] i2c-designware-pci: Add Haswell ULT device support Mika Westerberg
2014-04-06 13:54 ` Kirill A. Shutemov
2014-04-06 15:31 ` Wolfram Sang
2014-04-07 9:09 ` Mika Westerberg
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=1382326010-4554-1-git-send-email-bleung@chromium.org \
--to=bleung@chromium.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dlaurie@chromium.org \
--cc=jacmet@sunsite.dk \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@the-dreams.de \
/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®