lkml.org 
[lkml]   [2014]   [Feb]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 00/10] Support TI Light Management Unit devices
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


\
 
 \ /
  Last update: 2014-02-17 01:21    [W:0.039 / U:0.388 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site