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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140214101439.GA9462@lee--X1>
Date:	Fri, 14 Feb 2014 10:14:39 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Milo Kim <milo.kim@...com>
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

> 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`

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/