From: Greg KH <gregkh@linuxfoundation.org>
To: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Sibi Sankar <quic_sibis@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>
Subject: Re: [PATCH V1 0/3] Add notifier call chain to Embedded USB Debug(EUD) driver
Date: Thu, 13 Jul 2023 15:52:58 +0200 [thread overview]
Message-ID: <2023071328-siamese-brethren-0174@gregkh> (raw)
In-Reply-To: <d8987058-ee49-cdbd-0fc1-ed80829473b5@quicinc.com>
On Thu, Jul 13, 2023 at 01:55:34PM +0530, Souradeep Chowdhury wrote:
>
>
> On 7/12/2023 10:10 PM, Greg KH wrote:
> > On Wed, Jul 12, 2023 at 01:52:37PM +0530, Souradeep Chowdhury wrote:
> > > This patch series adds the notifier chain to the Embedded USB Debug(EUD) driver.
> > > The notifier chain is used to check the role switch status of EUD. Since EUD can
> > > function only in device mode, other modules trying to do role-switch on the same
> > > port have to first check the EUD status by calling this notifier chain and based
> > > on the status proceed or block their role-switching step. The modules can call
> > > the notifier through the call eud_notifier_call_chain and pass their own
> > > role switch state as the argument. This chain will also be able to handle the
> > > scenario of multiple modules switching roles on the same port since this can
> > > create a priority and ordering among them for conflict resolution.
> >
> > You are adding a new api that no one is actually using, so why would we
> > accept this at all?
> >
> > And how can we actually review it without any real users?
>
> Ack. The next version of this will be posted along with the usage
> of these apis for ordering the role-switch.
Also note that I hate notifier call chains, so you better have a very
good reason for why they are required and can't be done in any other
normal way instead :)
good luck!
greg k-h
next prev parent reply other threads:[~2023-07-13 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:22 [PATCH V1 0/3] Add notifier call chain to Embedded USB Debug(EUD) driver Souradeep Chowdhury
2023-07-12 8:22 ` [PATCH V1 1/3] usb: misc: Add the interface for notifier call for Embedded USB Debugger(EUD) Souradeep Chowdhury
2023-07-12 16:41 ` Greg KH
2023-07-12 8:22 ` [PATCH V1 2/3] usb: misc: Add notifier call chain to Embedded USB Debug(EUD) driver Souradeep Chowdhury
2023-07-12 18:22 ` Bhupesh Sharma
2023-07-13 8:30 ` Souradeep Chowdhury
2023-07-12 8:22 ` [PATCH V1 3/3] MAINTAINERS: Add the header file entry for Embedded USB debugger(EUD) Souradeep Chowdhury
2023-07-12 18:24 ` Bhupesh Sharma
2023-07-12 16:40 ` [PATCH V1 0/3] Add notifier call chain to Embedded USB Debug(EUD) driver Greg KH
2023-07-13 8:25 ` Souradeep Chowdhury
2023-07-13 13:52 ` Greg KH [this message]
2023-07-12 16:43 ` Konrad Dybcio
2023-07-13 8:26 ` Souradeep Chowdhury
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=2023071328-siamese-brethren-0174@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_schowdhu@quicinc.com \
--cc=quic_sibis@quicinc.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;
as well as URLs for NNTP newsgroup(s).