From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: dts: vf610: relicense the device trees under GPLv2/X11
Date: Mon, 07 Dec 2015 14:04:00 -0800 [thread overview]
Message-ID: <ac03ae2d77dc47b7cb6ff258e291865e@agner.ch> (raw)
In-Reply-To: <56660024.5020006@wwwdotorg.org>
On 2015-12-07 13:54, Stephen Warren wrote:
> On 12/07/2015 02:51 PM, Stefan Agner wrote:
>> I collected the Acks I received so far and removed them from the list
>> below. Several Freescale addresses are no longer valid (the once
>> starting with --)... I would interprete the Ack from Yuan Yao as an
>> Ack from Freescale.
>>
>> Matt, you introduced the vf610-cosmic.dts board, is it possible to
>> get an ack for this too? I think you did not receive v1 of this patch
>> due to an old email address, sorry about that.
>
> I thought I'd already sent an ack for this, but it looks like I forgot somehow.
>
> Acked-by: Stephen Warren <swarren@nvidia.com>
Sorry about the confusion, I do have your ack and hence removed you from
the list. However I still put everyone in CC, probably not what I should
have done?
--
Stefan
next prev parent reply other threads:[~2015-12-07 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 21:51 [PATCH v2 0/4] ARM: dts: vf610: relicense the device trees under GPLv2/X11 Stefan Agner
2015-12-07 21:51 ` [PATCH v2 1/4] ARM: dts: vf610: relicense vf???.dtsi " Stefan Agner
2015-12-07 21:51 ` [PATCH v2 2/4] ARM: dts: vf610-colibri: relicense vf*colibri* " Stefan Agner
2015-12-07 21:51 ` [PATCH v2 3/4] ARM: dts: vf610-cosmic: relicense vf610-cosmic.dts " Stefan Agner
2015-12-16 23:42 ` Stefan Agner
2016-01-28 0:36 ` Stefan Agner
2015-12-07 21:51 ` [PATCH v2 4/4] ARM: dts: vf610-twr: relicense vf610-twr.dts " Stefan Agner
2015-12-07 21:54 ` [PATCH v2 0/4] ARM: dts: vf610: relicense the device trees " Stephen Warren
2015-12-07 22:04 ` Stefan Agner [this message]
2016-02-03 1:00 ` Stefan Agner
2016-02-03 14:28 ` Shawn Guo
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=ac03ae2d77dc47b7cb6ff258e291865e@agner.ch \
--to=stefan@agner.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).