From: Florian Fainelli <f.fainelli@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org,
MTD Maling List <linux-mtd@lists.infradead.org>,
miquel.raynal@bootlin.com
Subject: Re: [PATCH] bcm963xx_tag.h: fix duplicated word
Date: Wed, 15 Jul 2020 19:06:36 -0700 [thread overview]
Message-ID: <847e3e46-2fc2-daea-67f3-3aaf0f2af4ac@gmail.com> (raw)
In-Reply-To: <d30c09a3-fe30-ddf1-3f21-00fc48b16443@infradead.org>
Le 2020-07-15 à 18:28, Randy Dunlap a écrit :
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Change doubled word "is" to "it is".
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: bcm-kernel-feedback-list@broadcom.com
> Cc: linux-mips@vger.kernel.org
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
This should probably be merged via linux-mips or linux-mtd, since we
have consumers of this header on both trees.
> ---
> include/linux/bcm963xx_tag.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20200714.orig/include/linux/bcm963xx_tag.h
> +++ linux-next-20200714/include/linux/bcm963xx_tag.h
> @@ -84,7 +84,7 @@ struct bcm_tag {
> char flash_layout_ver[FLASHLAYOUTVER_LEN];
> /* 196-199: kernel+rootfs CRC32 */
> __u32 fskernel_crc;
> - /* 200-215: Unused except on Alice Gate where is is information */
> + /* 200-215: Unused except on Alice Gate where it is information */
> char information2[TAGINFO2_LEN];
> /* 216-219: CRC32 of image less imagetag (kernel for Alice Gate) */
> __u32 image_crc;
>
--
Florian
next prev parent reply other threads:[~2020-07-16 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 1:28 [PATCH] bcm963xx_tag.h: fix duplicated word Randy Dunlap
2020-07-16 2:06 ` Florian Fainelli [this message]
2020-08-03 6:53 ` Miquel Raynal
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=847e3e46-2fc2-daea-67f3-3aaf0f2af4ac@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=rdunlap@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