linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Richter <rrichter@marvell.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: <jlu@pengutronix.de>, <bp@alien8.de>, <mchehab@kernel.org>,
	<tony.luck@intel.com>, <james.morse@arm.com>,
	<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] EDAC/armada_xp: Fix some log messages
Date: Tue, 14 Apr 2020 11:46:23 +0200	[thread overview]
Message-ID: <20200414094622.45hrvmf6lz24trgx@rric.localdomain> (raw)
In-Reply-To: <20200413041556.3514-1-christophe.jaillet@wanadoo.fr>

On 13.04.20 06:15:56, Christophe JAILLET wrote:
> Fix some spelling (s/Aramda/Armada/) in 1 log message and in 1 comment.
> 
> While at it, add some trailing '\n' in some other log message.
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>

Reviewed-by: Robert Richter <rrichter@marvell.com>

> ---
>  drivers/edac/armada_xp_edac.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)

Note there are some other "Aramda" occurrences in the kernel:

linux/master:Documentation/devicetree/bindings/rtc/armada-380-rtc.txt:  "marvell,armada-8k-rtc" for Aramda 7K/8K SoCs
linux/master:arch/arm64/boot/dts/marvell/armada-8020.dtsi:/* The RTC requires external oscillator. But on Aramda 80x0, the RTC clock
linux/master:arch/arm64/boot/dts/marvell/armada-8040.dtsi:/* The RTC requires external oscillator. But on Aramda 80x0, the RTC clock
linux/master:drivers/mtd/nand/raw/Kconfig:        - 64-bit Aramda platforms (7k, 8k) (NFCv2)

Thanks,

-Robert

  parent reply	other threads:[~2020-04-14  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  4:15 [PATCH] EDAC/armada_xp: Fix some log messages Christophe JAILLET
2020-04-14  8:23 ` Jan Lübbe
2020-04-14  9:46 ` Robert Richter [this message]
2020-04-14  9:47 ` Borislav Petkov

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=20200414094622.45hrvmf6lz24trgx@rric.localdomain \
    --to=rrichter@marvell.com \
    --cc=bp@alien8.de \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=james.morse@arm.com \
    --cc=jlu@pengutronix.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).