From: Milo Kim <milo.kim-l0cyMroinI0@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Jingoo Han <jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
Bryan Wu <cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [PATCH 00/10] Support TI Light Management Unit devices
Date: Mon, 17 Feb 2014 08:51:39 +0900 [thread overview]
Message-ID: <53014F0B.6010708@ti.com> (raw)
In-Reply-To: <20140214101439.GA9462@lee--X1>
Hi Lee,
On 02/14/2014 07:14 PM, Lee Jones wrote:
>> Milo Kim (10):
>> mfd: Add TI LMU driver
>> backlight: Add TI LMU backlight common driver
>> backlight: ti-lmu-backlight: Add LM3532 driver
>> backlight: ti-lmu-backlight: Add LM3631 driver
>> backlight: ti-lmu-backlight: Add LM3633 driver
>> backlight: ti-lmu-backlight: Add LM3695 driver
>> backlight: ti-lmu-backlight: Add LM3697 driver
>> leds: Add LM3633 driver
>> regulator: Add LM3631 driver
>> Documentation: Add device tree bindings for TI LMU devices
>
> It makes it much easier to track if you send your patch set (shallow)
> threaded i.e. all patches attached to [PATCH 0/x]. Having all of the
> patches sent individually they will get split up and spread out all
> over the reviewers INBOX, which becomes unwieldy very quickly.
>
> Please see git send-email options:
> `--[no-]thread` and `--[no-]chain-reply-to`
>
Oh, sorry. I made a mistake.
I copied patch files from my working machine and sent them by using git
send-email.
I should run
git send-email --thread --no-chain-reply-to *.patch
but I did for each patch file, stupidly.
git send-email --thread --no-chain-reply-to 0000-cover.patch
git send-email --thread --no-chain-reply-to
0001-mfd-Add-TI-LMU-driver.patch
..
git send-email --thread --no-chain-reply-to
0010-Documentation-Add-device-tree-bindings-for-TI-LMU-de.patch
I'm so embarrassed..
Thanks for your advice.
Best regards,
Milo
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Milo Kim <milo.kim@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Jingoo Han <jg1.han@samsung.com>, Bryan Wu <cooloney@gmail.com>,
Mark Brown <broonie@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 00/10] Support TI Light Management Unit devices
Date: Mon, 17 Feb 2014 08:51:39 +0900 [thread overview]
Message-ID: <53014F0B.6010708@ti.com> (raw)
In-Reply-To: <20140214101439.GA9462@lee--X1>
Hi Lee,
On 02/14/2014 07:14 PM, Lee Jones wrote:
>> Milo Kim (10):
>> mfd: Add TI LMU driver
>> backlight: Add TI LMU backlight common driver
>> backlight: ti-lmu-backlight: Add LM3532 driver
>> backlight: ti-lmu-backlight: Add LM3631 driver
>> backlight: ti-lmu-backlight: Add LM3633 driver
>> backlight: ti-lmu-backlight: Add LM3695 driver
>> backlight: ti-lmu-backlight: Add LM3697 driver
>> leds: Add LM3633 driver
>> regulator: Add LM3631 driver
>> Documentation: Add device tree bindings for TI LMU devices
>
> It makes it much easier to track if you send your patch set (shallow)
> threaded i.e. all patches attached to [PATCH 0/x]. Having all of the
> patches sent individually they will get split up and spread out all
> over the reviewers INBOX, which becomes unwieldy very quickly.
>
> Please see git send-email options:
> `--[no-]thread` and `--[no-]chain-reply-to`
>
Oh, sorry. I made a mistake.
I copied patch files from my working machine and sent them by using git
send-email.
I should run
git send-email --thread --no-chain-reply-to *.patch
but I did for each patch file, stupidly.
git send-email --thread --no-chain-reply-to 0000-cover.patch
git send-email --thread --no-chain-reply-to
0001-mfd-Add-TI-LMU-driver.patch
..
git send-email --thread --no-chain-reply-to
0010-Documentation-Add-device-tree-bindings-for-TI-LMU-de.patch
I'm so embarrassed..
Thanks for your advice.
Best regards,
Milo
next prev parent reply other threads:[~2014-02-16 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 6:30 [PATCH 00/10] Support TI Light Management Unit devices Milo Kim
2014-02-14 6:30 ` Milo Kim
2014-02-14 10:14 ` Lee Jones
2014-02-16 23:51 ` Milo Kim [this message]
2014-02-16 23:51 ` Milo Kim
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=53014F0B.6010708@ti.com \
--to=milo.kim-l0cymroini0@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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.