From: Maurus Cuelenaere <mcuelenaere@gmail.com>
To: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Michal Nazarewicz <m.nazarewicz@samsung.com>,
linux-usb <linux-usb@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Fabien Chouteau <fabien.chouteau@barco.com>,
david Brownell <dbrownell@users.sourceforge.net>,
Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>,
LKML <linux-kernel@vger.kernel.org>, MeeGo <meego-dev@meego.com>,
"Wang, Qi" <qi.wang@intel.com>,
"Wang, Yong Y" <yong.y.wang@intel.com>,
Andrew <andrew.chih.howe.khor@intel.com>,
Intel OTC <joel.clark@intel.com>,
"Foster, Margie" <margie.foster@intel.com>,
Arjan <arjan@linux.intel.com>,
Toshiharu Okada <okada533@dsn.okisemi.com>,
Takahiro Shimizu <shimizu394@dsn.okisemi.com>,
Tomoya Morinaga <morinaga526@dsn.okisemi.com>
Subject: Re: [PATCH] USB device driver of Topcliff PCH
Date: Mon, 13 Sep 2010 12:26:30 +0200 [thread overview]
Message-ID: <4C8DFC56.8020006@gmail.com> (raw)
In-Reply-To: <000a01cb52fb$78fc2310$66f8800a@maildom.okisemi.com>
Op 13-09-10 06:23, Masayuki Ohtake schreef:
> Hi Maurus
Hi Ohtake,
>
> My reply comments are included in the following.
> I will resubmit after modified
>
> Thanks Ohtake
>
> From: Maurus Cuelenaere <mcuelenaere@gmail.com>
> Date: Tue, 7 Sep 2010 14:53:05 +0200
>> 2010/9/7 Masayuki Ohtake <masa-korg@dsn.okisemi.com>
>>> This patch adds the USB device driver of Topcliff PCH.
>>> Topcliff PCH is the platform controller hub that is going to be used in
>>> Intel's upcoming general embedded platform. All IO peripherals in
>>> Topcliff PCH are actually devices sitting on AMBA bus.
>>> Topcliff PCH has USB device I/F. Using this I/F, it is able to access system
>>> devices connected to USB device.
>>>
>>> Signed-off-by: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
>> No need to mail all these people, just the maintainers and appropriate mailing
>> lists will do.
> [masa]
> I have question. Please tell me.
> Whom should I submit patch to?
> TO: LKML and maintainers
> Is it correct?
>
> The maintainer was got the following scripts.
> "./scripts/get_maintainer.pl"
If you do scripts/get_maintainer.pl --rolestats <patch>, you'll see why
get_maintainer.pl picked these persons. I generally CC anyone that's "above"
commit_signer or that I know has an important relation to the patch (e.g. the
author of a driver you're editing).
If there are any mailing lists listed (linux-usb in this case), be sure to CC
them too (except LKML, I wouldn't CC them unless it's a special case like the
changes are kernel-wide or need to reviewed by a wide variation of audience or
...)
IIRC, these rules are also explained at Documentation/Submit*.
--
Maurus Cuelenaere
next prev parent reply other threads:[~2010-09-13 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 7:49 [PATCH] USB device driver of Topcliff PCH Masayuki Ohtake
2010-09-07 12:53 ` Maurus Cuelenaere
2010-09-13 4:23 ` Masayuki Ohtake
2010-09-13 10:26 ` Maurus Cuelenaere [this message]
2010-09-13 11:31 ` Michał Nazarewicz
2010-09-14 8:35 ` Masayuki Ohtake
2010-09-14 12:50 ` Maurus Cuelenaere
2010-09-14 17:33 ` Valdis.Kletnieks
2010-09-08 0:22 ` Greg KH
2010-09-13 4:23 ` Masayuki Ohtake
2010-09-13 15:29 ` Greg KH
2010-09-08 1:58 ` Michał Nazarewicz
2010-09-08 13:57 ` Masayuki Ohtake
2010-09-13 4:23 ` Masayuki Ohtake
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=4C8DFC56.8020006@gmail.com \
--to=mcuelenaere@gmail.com \
--cc=andrew.chih.howe.khor@intel.com \
--cc=arjan@linux.intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=fabien.chouteau@barco.com \
--cc=gregkh@suse.de \
--cc=joel.clark@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.nazarewicz@samsung.com \
--cc=margie.foster@intel.com \
--cc=masa-korg@dsn.okisemi.com \
--cc=meego-dev@meego.com \
--cc=morinaga526@dsn.okisemi.com \
--cc=nicolas.ferre@atmel.com \
--cc=okada533@dsn.okisemi.com \
--cc=peter.korsgaard@barco.com \
--cc=qi.wang@intel.com \
--cc=randy.dunlap@oracle.com \
--cc=shimizu394@dsn.okisemi.com \
--cc=siccegge@stud.informatik.uni-erlangen.de \
--cc=yong.y.wang@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