From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers/usb/: Simplify return statements
Date: Fri, 31 Jul 2015 09:00:08 -0500 [thread overview]
Message-ID: <20150731140008.GD31041@saruman.tx.rr.com> (raw)
In-Reply-To: <20150731050558.GA2481@alcatraz>
Hi,
(no top-posting)
On Fri, Jul 31, 2015 at 05:06:07AM +0000, Karajgaonkar, Saurabh (S.) wrote:
> Sure, I'll do that. Just wanted to know whether I should split the
> patches and send them in this same mail thread (may be something like
> [PATCH 01/04 V2]) or should I start new threads and send them
> separately to the respective maintainers.
single thread is fine, maintainers will pick single patches.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150731/2e1b76f8/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@ti.com>
To: "Karajgaonkar, Saurabh (S.)" <skarajga@visteon.com>
Cc: Felipe Balbi <balbi@ti.com>,
"srinivas.kandagatla@gmail.com" <srinivas.kandagatla@gmail.com>,
"maxime.coquelin@st.com" <maxime.coquelin@st.com>,
"patrice.chotard@st.com" <patrice.chotard@st.com>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"mathias.nyman@intel.com" <mathias.nyman@intel.com>,
"johan@kernel.org" <johan@kernel.org>,
"sergei.shtylyov@cogentembedded.com"
<sergei.shtylyov@cogentembedded.com>,
"Julia.Lawall@lip6.fr" <Julia.Lawall@lip6.fr>,
"khilman@linaro.org" <khilman@linaro.org>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"pmladek@suse.cz" <pmladek@suse.cz>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kernel@stlinux.com" <kernel@stlinux.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/usb/: Simplify return statements
Date: Fri, 31 Jul 2015 09:00:08 -0500 [thread overview]
Message-ID: <20150731140008.GD31041@saruman.tx.rr.com> (raw)
In-Reply-To: <20150731050558.GA2481@alcatraz>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi,
(no top-posting)
On Fri, Jul 31, 2015 at 05:06:07AM +0000, Karajgaonkar, Saurabh (S.) wrote:
> Sure, I'll do that. Just wanted to know whether I should split the
> patches and send them in this same mail thread (may be something like
> [PATCH 01/04 V2]) or should I start new threads and send them
> separately to the respective maintainers.
single thread is fine, maintainers will pick single patches.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-31 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:13 [PATCH] drivers/usb/: Simplify return statements Karajgaonkar, Saurabh (S.)
2015-07-30 13:13 ` Karajgaonkar, Saurabh (S.)
2015-07-30 16:25 ` Felipe Balbi
2015-07-30 16:25 ` Felipe Balbi
2015-07-31 5:06 ` Karajgaonkar, Saurabh (S.)
2015-07-31 5:06 ` Karajgaonkar, Saurabh (S.)
2015-07-31 14:00 ` Felipe Balbi [this message]
2015-07-31 14:00 ` 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=20150731140008.GD31041@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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.