From: slemieux.tyco@gmail.com (Sylvain Lemieux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] ARM: dts: lpc32xx: ea3250: fix Atmel at24 eeprom vendor
Date: Tue, 26 Apr 2016 11:41:44 -0400 [thread overview]
Message-ID: <1461685304.9433.6.camel@localhost> (raw)
In-Reply-To: <1461631050-10479-4-git-send-email-vz@mleia.com>
On Tue, 2016-04-26 at 03:37 +0300, Vladimir Zapolskiy wrote:
> There is no 'at' hardware vendor defined yet, correct vendor prefix
> for Atmel is 'atmel'.
>
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
> ---
> arch/arm/boot/dts/ea3250.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Acked-by: Sylvain Lemieux <slemieux.tyco@gmail.com>
next prev parent reply other threads:[~2016-04-26 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 0:37 [PATCH 0/7] ARM: dts: lpc32xx: nonfunctional updates to ea3250 and phy3250 dts Vladimir Zapolskiy
2016-04-26 0:37 ` [PATCH 1/7] ARM: dts: lpc32xx: ea3250: avoid extension of device nodes by absolute path Vladimir Zapolskiy
2016-04-26 15:45 ` Sylvain Lemieux
2016-04-26 0:37 ` [PATCH 2/7] ARM: dts: lpc32xx: ea3250: add NAND partitions device node Vladimir Zapolskiy
2016-04-26 16:58 ` Sylvain Lemieux
2016-04-26 18:36 ` Vladimir Zapolskiy
2016-04-26 0:37 ` [PATCH 3/7] ARM: dts: lpc32xx: ea3250: fix Atmel at24 eeprom vendor Vladimir Zapolskiy
2016-04-26 15:41 ` Sylvain Lemieux [this message]
2016-04-26 0:37 ` [PATCH 4/7] ARM: dts: lpc32xx: ea3250: add SoC name prefix to board dts file Vladimir Zapolskiy
2016-04-26 15:36 ` Sylvain Lemieux
2016-04-26 0:37 ` [PATCH 5/7] ARM: dts: lpc32xx: phy3250: avoid extension of device nodes by absolute path Vladimir Zapolskiy
2016-04-26 15:46 ` Sylvain Lemieux
2016-04-26 0:37 ` [PATCH 6/7] ARM: dts: lpc32xx: phy3250: add NAND partitions device node Vladimir Zapolskiy
2016-04-26 0:37 ` [PATCH 7/7] ARM: dts: lpc32xx: phy3250: add SoC name prefix to board dts file Vladimir Zapolskiy
2016-04-26 15:37 ` Sylvain Lemieux
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=1461685304.9433.6.camel@localhost \
--to=slemieux.tyco@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 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).