From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Danny Kaehn <kaehndan@gmail.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
jikos@kernel.org, benjamin.tissoires@redhat.com,
bartosz.golaszewski@linaro.org, dmitry.torokhov@gmail.com,
devicetree@vger.kernel.org, linux-input@vger.kernel.org,
ethan.twardy@plexus.com
Subject: Re: [PATCH v7 0/3] Firmware Support for USB-HID Devices and CP2112
Date: Fri, 24 Feb 2023 18:43:28 +0200 [thread overview]
Message-ID: <Y/jpME2mb5CqPooj@smile.fi.intel.com> (raw)
In-Reply-To: <20230223213147.268-1-kaehndan@gmail.com>
On Thu, Feb 23, 2023 at 03:31:44PM -0600, Danny Kaehn wrote:
> This patchset allows USB-HID devices to have DeviceTree bindings through sharing
> the USB fwnode with the HID driver, and adds such a binding and driver
> implementation for the CP2112 USB to SMBus Bridge (which necessitated the
> USB-HID change). This change allows a CP2112 permanently attached in hardware to
> be described in DT and interoperate with other drivers.
It's your responsibility to carry the tags you have got in the previous rounds
of the review. Please, be respectful to the reviewers who spent a lot of time
on yours, in particular, code. Otherwise why to bother with it (upstreaming)
at all?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-02-24 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:31 [PATCH v7 0/3] Firmware Support for USB-HID Devices and CP2112 Danny Kaehn
2023-02-23 21:31 ` [PATCH v7 1/3] dt-bindings: i2c: Add CP2112 HID USB to SMBus Bridge Danny Kaehn
2023-02-23 21:31 ` [PATCH v7 2/3] HID: usbhid: Share USB device firmware node with child HID device Danny Kaehn
2023-02-23 21:31 ` [PATCH v7 3/3] HID: cp2112: Fwnode Support Danny Kaehn
2023-02-24 16:43 ` Andy Shevchenko [this message]
2023-02-24 17:48 ` [PATCH v7 0/3] Firmware Support for USB-HID Devices and CP2112 Daniel Kaehn
2023-02-24 20:56 ` Andy Shevchenko
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=Y/jpME2mb5CqPooj@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=benjamin.tissoires@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ethan.twardy@plexus.com \
--cc=jikos@kernel.org \
--cc=kaehndan@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).