linux-kernel - Re: [PATCH 00/10] Support TI Light Management Unit devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53014F0B.6010708@ti.com>
Date:	Mon, 17 Feb 2014 08:51:39 +0900
From:	Milo Kim <milo.kim@...com>
To:	Lee Jones <lee.jones@...aro.org>
CC:	Jingoo Han <jg1.han@...sung.com>, Bryan Wu <cooloney@...il.com>,
	Mark Brown <broonie@...nel.org>,
	<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: [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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/