public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daehwan Jung <dh10.jung@samsung.com>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "open list:USB XHCI DRIVER" <linux-usb@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Howard Yen <howardyen@google.com>,
	Jack Pham <jackp@codeaurora.org>, Puma Hsu <pumahsu@google.com>,
	"J . Avila" <elavila@google.com>,
	sc.suh@samsung.com, cpgs@samsung.com, cpgsproxy5@samsung.com
Subject: Re: [PATCH v2 1/4] usb: host: export symbols for xhci hooks usage
Date: Tue, 8 Mar 2022 16:38:39 +0100	[thread overview]
Message-ID: <901bc0fb-8963-49c9-e838-dc6dc358a1d0@kernel.org> (raw)
In-Reply-To: <1646648256-105214-2-git-send-email-dh10.jung@samsung.com>

On 07/03/2022 11:17, Daehwan Jung wrote:
> Export symbols for xhci hooks usage:
> 	xhci_ring_free
> 	- Allow xhci hook to free xhci_ring.
> 

Please do not ignore comments of reviewers. Either you discuss with
them, or you implement. Ignoring is a non-cooperative choice.

Address first comments you received in v1.


Best regards,
Krzysztof

  reply	other threads:[~2022-03-08 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220307101848epcas2p1bc9c7992d4b25f78b37c7ca4672f1066@epcas2p1.samsung.com>
2022-03-07 10:17 ` [PATCH v2 0/4] support USB offload feature Daehwan Jung
2022-03-07 10:17   ` [PATCH v2 1/4] usb: host: export symbols for xhci hooks usage Daehwan Jung
2022-03-08 15:38     ` Krzysztof Kozlowski [this message]
2022-03-07 10:17   ` [PATCH v2 2/4] usb: host: add xhci hooks for USB offload Daehwan Jung
2022-03-07 10:17   ` [PATCH v2 3/4] usb: host: add some to xhci overrides " Daehwan Jung
2022-03-07 10:17   ` [PATCH v2 4/4] usb: host: add xhci-exynos module Daehwan Jung
2022-03-07 10:31     ` Greg Kroah-Hartman
2022-03-07 16:42     ` Christoph Hellwig
2022-03-08 15:37     ` Krzysztof Kozlowski

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=901bc0fb-8963-49c9-e838-dc6dc358a1d0@kernel.org \
    --to=krzk@kernel.org \
    --cc=cpgs@samsung.com \
    --cc=cpgsproxy5@samsung.com \
    --cc=dh10.jung@samsung.com \
    --cc=elavila@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=howardyen@google.com \
    --cc=jackp@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pumahsu@google.com \
    --cc=sc.suh@samsung.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