From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>, Len Brown <lenb@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: acpi: Do not create i2c-clients for LNXVIDEO ACPI devices
Date: Mon, 03 Jul 2017 18:48:54 +0300 [thread overview]
Message-ID: <1499096934.22624.241.camel@linux.intel.com> (raw)
In-Reply-To: <3a2b63d6-d88e-aae8-d8a1-a6203a8e971e@redhat.com>
On Mon, 2017-07-03 at 17:04 +0200, Hans de Goede wrote:
> On 03-07-17 13:10, Andy Shevchenko wrote:
> > On Sat, 2017-07-01 at 12:03 +0200, Hans de Goede wrote:
> > > This commit makes the i2c-core ignore LNXVIDEO compatible ACPI
> > > devices
> > > which has 2 positive results:
> > >
> > > 1) The bogus i2c-client for these is no longer created.
> > > 2) i2c_acpi_lookup_speed now ignores the 100KHz speed from the
> > > pseudo
> > > i2c-resouce and properly returns 400KHz as speed for the
> > > touchscreen
> > > i2c bus, fixing the touchscreen not working on various devies.
> >
> > Should it have Fixes tag?
>
> Well it is a fix, but it does not fix one specific commit, so no
> I don't think it should.
One may put several Fixes tags to make it clear that it applies on top
of the tree that has all of them (in the given sequence AFAIR).
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-07-03 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 10:03 [PATCH] i2c: acpi: Do not create i2c-clients for LNXVIDEO ACPI devices Hans de Goede
2017-07-03 11:10 ` Andy Shevchenko
2017-07-03 15:04 ` Hans de Goede
2017-07-03 15:48 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-04 12:46 Hans de Goede
2017-07-04 12:47 ` Hans de Goede
2017-07-04 12:49 ` Wolfram Sang
2017-07-04 12:50 ` Hans de Goede
2017-07-04 12:49 ` Andy Shevchenko
2017-07-04 12:51 ` Hans de Goede
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=1499096934.22624.241.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lenb@kernel.org \
--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).