From: Thierry Reding <thierry.reding@gmail.com>
To: Jim Lin <jilin@nvidia.com>
Cc: gregkh@linuxfoundation.org, jonathanh@nvidia.com,
mathias.nyman@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v7 2/3] xhci: hub: export symbol on xhci_hub_control
Date: Thu, 17 Nov 2022 23:30:06 +0100 [thread overview]
Message-ID: <Y3a17s9Usnlu66nH@orome> (raw)
In-Reply-To: <20221111101813.32482-3-jilin@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Fri, Nov 11, 2022 at 06:18:12PM +0800, Jim Lin wrote:
> XHCI host drivers may override the default xhci_hub_control() with
> their own device specific function. To allow these host drivers to
> call the xhci_hub_control() function from within their own
> hub_control() callback and be built as a module, export the symbol
> for xhci_hub_control.
>
> Signed-off-by: Jim Lin <jilin@nvidia.com>
>
> ---
> v5: new change
> v6: modify commit message
> v7: change commit message
>
> drivers/usb/host/xhci-hub.c | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-17 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 10:18 [PATCH v7 0/3] xhci: tegra: USB2 pad power controls Jim Lin
2022-11-11 10:18 ` [PATCH v7 1/3] xhci: Add hub_control to xhci_driver_overrides Jim Lin
2022-11-11 14:39 ` Jon Hunter
2022-11-17 22:29 ` Thierry Reding
2022-11-11 10:18 ` [PATCH v7 2/3] xhci: hub: export symbol on xhci_hub_control Jim Lin
2022-11-11 14:39 ` Jon Hunter
2022-11-17 22:30 ` Thierry Reding [this message]
2022-11-11 10:18 ` [PATCH v7 3/3] xhci: tegra: USB2 pad power controls Jim Lin
2022-11-11 14:42 ` Jon Hunter
2022-11-17 22:30 ` Thierry Reding
2023-01-06 14:56 ` [PATCH v7 0/3] " Jon Hunter
2023-01-06 15:25 ` Greg KH
2023-01-09 8:28 ` Mathias Nyman
2023-01-16 11:50 ` Jon Hunter
2023-01-16 12:23 ` Greg KH
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=Y3a17s9Usnlu66nH@orome \
--to=thierry.reding@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jilin@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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 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.