From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Christian Fetzer <fetzer.ch@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] i2c-piix4: Better bus names
Date: Sun, 31 Jan 2016 09:46:29 +0100 [thread overview]
Message-ID: <20160131094629.42e430ac@endymion.delvare> (raw)
In-Reply-To: <20160129101749.GB2053@tetsubishi>
On Fri, 29 Jan 2016 11:17:49 +0100, Wolfram Sang wrote:
> On Wed, Jan 27, 2016 at 02:40:33PM +0100, Jean Delvare wrote:
> > The I2C bus names are supposed to be stable as they can be used by
> > userspace to uniquely identify a specific I2C bus. So restore the
> > original names for all legacy (pre-SB800) devices.
> >
> > For SB800 devices and later, improve the names. "SDA" refers to the
> > serial data pin of each SMBus port, it's an implementation detail the
> > user doesn't need to know. Use "port" instead, which is easier to
> > understand.
> >
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Cc: Christian Fetzer <fetzer.ch@gmail.com>
> > Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Cc: Wolfram Sang <wsa@the-dreams.de>
>
> Changed the subject to "don't regress on bus names" and applied to
> for-current, thanks!
Thanks.
> Jean, could you use the "i2c: <driver>: <subject>" (check git log for
> examples) pattern for your future patches? Thanks!
OK, I will do that.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2016-01-31 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:40 [PATCH] i2c-piix4: Better bus names Jean Delvare
2016-01-27 15:03 ` Mika Westerberg
2016-01-27 18:49 ` Christian Fetzer
2016-01-29 10:17 ` Wolfram Sang
2016-01-31 8:46 ` Jean Delvare [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=20160131094629.42e430ac@endymion.delvare \
--to=jdelvare@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fetzer.ch@gmail.com \
--cc=linux-i2c@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;
as well as URLs for NNTP newsgroup(s).