From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wentong Wu <wentong.wu@intel.com>
Cc: hdegoede@redhat.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: misc: ljca: Drop _ADR support to get ljca children devices
Date: Tue, 14 Nov 2023 13:51:27 +0200 [thread overview]
Message-ID: <ZVNfPyuNS7Drzo3u@smile.fi.intel.com> (raw)
In-Reply-To: <20231114072531.1366753-1-wentong.wu@intel.com>
On Tue, Nov 14, 2023 at 03:25:31PM +0800, Wentong Wu wrote:
> Currently the shipped platforms use only _HID to distinguish
> ljca children devices. The _ADR support here is for future HW.
> This patch is to drop _ADR support and we can then re-introduce
> it (revert this patch) if future HW actually starts using _ADR
> to distinguish children devices.
Thank you!
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-11-14 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 7:25 [PATCH] usb: misc: ljca: Drop _ADR support to get ljca children devices Wentong Wu
2023-11-14 10:26 ` Hans de Goede
2023-11-14 11:51 ` 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=ZVNfPyuNS7Drzo3u@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=wentong.wu@intel.com \
/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