From: Felipe Balbi <balbi@ti.com>
To: Yang Ruirui <ruirui.r.yang@tieto.com>
Cc: Felipe Balbi <balbi@ti.com>,
Yang Ruirui R <ruirui.r.yang@tietoenator.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Mian Yousaf Kaukab <mian.yousaf.kaukab@stericsson.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Felipe Balbi <felipe.balbi@nokia.com>,
Heikki Krogerus <ext-heikki.krogerus@nokia.com>,
Tejun Heo <tj@kernel.org>, Samuel Ortiz <sameo@linux.intel.com>,
Hema HK <hemahk@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb otg: use atomic notifier instead of blocking notifier
Date: Thu, 20 Jan 2011 06:01:00 +0200 [thread overview]
Message-ID: <20110120040059.GA2389@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20110120020638.GA24396@darkstar>
On Thu, Jan 20, 2011 at 10:06:38AM +0800, Yang Ruirui wrote:
> Actually I does not found where notifiers are used in these files except
> langwell_otg
>
> For langwell_otg.c there's a wrapper struct named "intel mid_otg_xceiv"
> in include/linux/usb/intel_mid_otg.h, it use an atomic notifier for
> interrupt context.
>
> So I think we'd better write another patch to make it use general
> otg_transceiver for notifier or just keep current code. What's your opinion?
I'm not the maintainer but I would rather see it using the notifier on
the otg_transceiver structure, and later add the support for the other
transceivers too.
--
balbi
next prev parent reply other threads:[~2011-01-20 4:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 9:20 Yang Ruirui
2011-01-19 10:33 ` Heikki Krogerus
2011-01-21 15:34 ` Grazvydas Ignotas
2011-01-19 10:40 ` Felipe Balbi
2011-01-20 2:06 ` Yang Ruirui
2011-01-20 4:01 ` Felipe Balbi [this message]
2011-01-19 15:18 ` Ming Lei
2011-01-19 15:30 ` Felipe Balbi
2011-01-19 15:38 ` Ming Lei
2011-01-19 16:01 ` Felipe Balbi
2011-01-20 15:51 ` Mian Yousaf Kaukab
2011-01-19 9:22 Yang Ruirui
2011-01-19 9:19 ` Dave Young
2011-01-20 6:46 ` Felipe Balbi
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=20110120040059.GA2389@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=ext-heikki.krogerus@nokia.com \
--cc=felipe.balbi@nokia.com \
--cc=gregkh@suse.de \
--cc=hemahk@ti.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mian.yousaf.kaukab@stericsson.com \
--cc=ruirui.r.yang@tieto.com \
--cc=ruirui.r.yang@tietoenator.com \
--cc=sameo@linux.intel.com \
--cc=tj@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
all inboxes | Powered by JetHome®