All of lore.kernel.org
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Add dts entries for mvebu and dove
Date: Fri, 06 Feb 2015 14:42:52 +0100	[thread overview]
Message-ID: <54D4C4DC.4070208@gmail.com> (raw)
In-Reply-To: <54D4C1C3.1010209@free-electrons.com>

On 06.02.2015 14:29, Gregory CLEMENT wrote:
> On 06/02/2015 14:18, Jason Cooper wrote:
>> On 2/6/15 7:30 AM, Gregory CLEMENT wrote:
>>> Since many releases, the modifications of the mvebu device tree files
>>> are merged through the mvebu subsystem. This patch makes it official
>>> in order to help the contributors using the get_maintainer.pl to find
>>> the accurate people.
>>>
>>> In the same time, updated the mvebu description which now includes the
>>> kirkwood SoCs and new Armada SoCs.
>>>
>>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>>>    ARM/Marvell Berlin SoC support
>>>    M:	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
>>
>> It's just in the context, but I'm sure Sebastian wouldn't mind
>> if we did berlin as well in this patch.
>
> Sebastian,
> if you agree I will add your entries, and rename the patch to
>
> [PATCH] MAINTAINERS: Add dts entries for some of the Marvell Socs

Gregory,

yes, I agree. Feel free to add my

Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>

for the updated patch already.

Thanks!

  reply	other threads:[~2015-02-06 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 12:30 [PATCH] MAINTAINERS: Add dts entries for mvebu and dove Gregory CLEMENT
2015-02-06 13:18 ` Jason Cooper
2015-02-06 13:29   ` Gregory CLEMENT
2015-02-06 13:42     ` Sebastian Hesselbarth [this message]
2015-02-06 13:46       ` Jason Cooper
2015-02-06 14:16 ` Andrew Lunn

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=54D4C4DC.4070208@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.