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 0/2] ARM: add initial support for the Marvell BG2-Q DMP
Date: Thu, 13 Mar 2014 09:51:29 +0000	[thread overview]
Message-ID: <53217FA1.4020903@gmail.com> (raw)
In-Reply-To: <20140312113523.GL13905@piout.net>

On 03/12/2014 11:35 AM, Alexandre Belloni wrote:
> On 12/03/2014 at 12:06:02 +0100, Antoine T?nart wrote :
>> This serie adds the initial support for the Marvell BG2-Q DMP (part of the
>> Berlin family). SoC has nodes for cpu, l2 cache controller, interrupt
>> controllers, local timer, apb timers and uarts for now.
>>
>> Homepage: http://www.marvell.com/digital-entertainment/armada-1500-pro/
>>
>
> I would move that description to the commit logs. Else one would have to
> lookup the mailing list archive to read it.

Antoine,

thanks for posting this. I also prefer each patch to have a commit log
no matter how obvious the contents may be. Please have a simple commit
log for each of the single patches.

You can leave out the link to marvell.com in the commit log as you
update Marvell SoC documentation.

TBH, I haven't set up any mach-berlin branches, yet. Also it is very
late in the cycle. I'll setup proper branches and also a -next branch
for next release, maybe we can take your DT patches directly through
arm-soc this time. Otherwise, we'll have to postpone them for v3.16.

I have some comments on the single patches and will reply there.

Sebastian

WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: "Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
	"Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: zmxu@marvell.com, jszhang@marvell.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ARM: add initial support for the Marvell BG2-Q DMP
Date: Thu, 13 Mar 2014 09:51:29 +0000	[thread overview]
Message-ID: <53217FA1.4020903@gmail.com> (raw)
In-Reply-To: <20140312113523.GL13905@piout.net>

On 03/12/2014 11:35 AM, Alexandre Belloni wrote:
> On 12/03/2014 at 12:06:02 +0100, Antoine Ténart wrote :
>> This serie adds the initial support for the Marvell BG2-Q DMP (part of the
>> Berlin family). SoC has nodes for cpu, l2 cache controller, interrupt
>> controllers, local timer, apb timers and uarts for now.
>>
>> Homepage: http://www.marvell.com/digital-entertainment/armada-1500-pro/
>>
>
> I would move that description to the commit logs. Else one would have to
> lookup the mailing list archive to read it.

Antoine,

thanks for posting this. I also prefer each patch to have a commit log
no matter how obvious the contents may be. Please have a simple commit
log for each of the single patches.

You can leave out the link to marvell.com in the commit log as you
update Marvell SoC documentation.

TBH, I haven't set up any mach-berlin branches, yet. Also it is very
late in the cycle. I'll setup proper branches and also a -next branch
for next release, maybe we can take your DT patches directly through
arm-soc this time. Otherwise, we'll have to postpone them for v3.16.

I have some comments on the single patches and will reply there.

Sebastian


  reply	other threads:[~2014-03-13  9:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 11:06 [PATCH 0/2] ARM: add initial support for the Marvell BG2-Q DMP Antoine Ténart
2014-03-12 11:06 ` Antoine Ténart
2014-03-12 11:06 ` [PATCH 1/2] ARM: dts: berlin2q: add the Marvell Armada 1500 pro (BG2Q) device tree Antoine Ténart
2014-03-12 11:06   ` Antoine Ténart
2014-03-12 12:22   ` Alexandre Belloni
2014-03-12 12:22     ` Alexandre Belloni
2014-03-13  9:56     ` Sebastian Hesselbarth
2014-03-13  9:56       ` Sebastian Hesselbarth
2014-03-13 10:08       ` Alexandre Belloni
2014-03-13 10:08         ` Alexandre Belloni
2014-03-13 10:17         ` Sebastian Hesselbarth
2014-03-13 10:17           ` Sebastian Hesselbarth
2014-03-13 10:27           ` Antoine Ténart
2014-03-13 10:27             ` Antoine Ténart
2014-03-13 10:05   ` Sebastian Hesselbarth
2014-03-13 10:05     ` Sebastian Hesselbarth
2014-03-13 10:43     ` Alexandre Belloni
2014-03-13 10:43       ` Alexandre Belloni
2014-03-13 11:02       ` Jisheng Zhang
2014-03-13 11:02         ` Jisheng Zhang
2014-03-12 11:06 ` [PATCH 2/2] ARM: dts: berlin2q: add the Marvell BG2-Q DMP " Antoine Ténart
2014-03-12 11:06   ` Antoine Ténart
2014-03-12 11:20   ` Arnd Bergmann
2014-03-12 11:20     ` Arnd Bergmann
2014-03-12 11:30     ` Antoine Ténart
2014-03-12 11:30       ` Antoine Ténart
2014-03-12 12:04   ` Jisheng Zhang
2014-03-12 12:04     ` Jisheng Zhang
2014-03-12 12:37     ` Andrew Lunn
2014-03-12 12:37       ` Andrew Lunn
2014-03-12 12:44       ` Jisheng Zhang
2014-03-12 12:44         ` Jisheng Zhang
2014-03-13 10:08   ` Sebastian Hesselbarth
2014-03-13 10:08     ` Sebastian Hesselbarth
2014-03-12 11:35 ` [PATCH 0/2] ARM: add initial support for the Marvell BG2-Q DMP Alexandre Belloni
2014-03-12 11:35   ` Alexandre Belloni
2014-03-13  9:51   ` Sebastian Hesselbarth [this message]
2014-03-13  9:51     ` Sebastian Hesselbarth
2014-03-13  9:56     ` Alexandre Belloni
2014-03-13  9:56       ` Alexandre Belloni
2014-03-13 10:35     ` Antoine Ténart
2014-03-13 10:35       ` Antoine Ténart

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=53217FA1.4020903@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.