From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/1] ACPI / scan: Create platform device for BSG2150 ACPI nodes
Date: Tue, 5 Feb 2019 17:55:08 +0200 [thread overview]
Message-ID: <CAHp75Vczx8+-Ut0mzB_weT3W6OWYKvd8L2wT+9TXZ-wSxSGToA@mail.gmail.com> (raw)
In-Reply-To: <20181220143451.25962-1-hdegoede@redhat.com>
On Thu, Dec 20, 2018 at 4:35 PM Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi All,
>
> This patch adds support for another ACPI HID which describes multiple
> i2c-clients in a single node. As such this applies on top of the recent
> patch from Andy making a similar change for INT3515 nodes:
>
> Commit a3dd034a1707 ("ACPI / scan: Create platform device for INT3515
> ACPI nodes"), which is in the platform-drivers-x86-v4.21-1 tag.
>
> As such I believe it would be best to merge this tree through the
> linux-platform-drivers-x86 tree, as was done for the INT3515 patch.
>
> Rafael, may we have your ack for merging the single line drivers/acpi
> change through the linux-platform-drivers-x86 tree?
>
Pushed to my review and testing queue, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-02-05 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 14:34 [PATCH 0/1] ACPI / scan: Create platform device for BSG2150 ACPI nodes Hans de Goede
2018-12-20 14:34 ` [PATCH] " Hans de Goede
2018-12-20 20:59 ` Rafael J. Wysocki
2019-02-05 15:55 ` Andy Shevchenko [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=CAHp75Vczx8+-Ut0mzB_weT3W6OWYKvd8L2wT+9TXZ-wSxSGToA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.