All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Milo Kim <milo.kim@ti.com>
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: Fri, 14 Feb 2014 10:14:39 +0000	[thread overview]
Message-ID: <20140214101439.GA9462@lee--X1> (raw)
In-Reply-To: <1392359410-6852-1-git-send-email-milo.kim@ti.com>

> 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

  reply	other threads:[~2014-02-14 10:14 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 [this message]
2014-02-16 23:51   ` Milo Kim
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=20140214101439.GA9462@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=cooloney@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jg1.han@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milo.kim@ti.com \
    --cc=sameo@linux.intel.com \
    /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.