From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Tom Hebb <tommyhebb@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: [PATCH 0/3] Documentation: arm: update Berlin family info in Marvell README
Date: Thu, 19 Nov 2015 21:15:28 +0100 [thread overview]
Message-ID: <564E2DE0.8010702@gmail.com> (raw)
In-Reply-To: <5647EFB3.8080904@gmail.com>
On 15.11.2015 03:36, Tom Hebb wrote:
> These are a few changes to bring the Marvell Berlin family documentation
> up to date. The old URLs were no longer redirecting properly, so I
> changed them to the current ones. I also added what information I could
> find about the new BG2CDP chip used in the Chromecast 2015.
>
> Thomas Hebb (3):
> Documentation: arm: update homepage URLs for Marvell Berlin SoCs
> Documentation: arm: add Marvell Armada 1500 Mini Plus to SoC list
> Documentation: arm: remove hyphen from BG2Q in Marvell Berlin docs
>
> Documentation/arm/Marvell/README | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
Thomas,
thanks for the cleanup and update! Somehow, your series
misses the in-reply-to tag which makes the individual
patches kind of hard to track.
I have applied all 3 patches (v2 for 2/3) to berlin/doc that
I can send a PR for to Jonathan.
If Jonathan prefers to pick-up the patches himself, feel free
to add my
Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Sebastian
prev parent reply other threads:[~2015-11-19 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 2:36 [PATCH 0/3] Documentation: arm: update Berlin family info in Marvell README Tom Hebb
2015-11-19 20:15 ` Sebastian Hesselbarth [this message]
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=564E2DE0.8010702@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=corbet@lwn.net \
--cc=gregory.clement@free-electrons.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tommyhebb@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox