From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: xinhui <xinhui.pan@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Andrzej Hajda <a.hajda@samsung.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
Hari Bathini <hbathini@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
tglx@linutronix.de, Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: powerpc/nvram: Fix an incorrect partition merge
Date: Tue, 20 Sep 2016 23:07:19 +1000 (AEST) [thread overview]
Message-ID: <3sdjhm0b28z9t0m@ozlabs.org> (raw)
In-Reply-To: <566929FA.2050409@linux.vnet.ibm.com>
On Thu, 2015-10-12 at 07:30:02 UTC, xinhui wrote:
> From: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
>
> When we merge two contiguous partitions whose signatures are marked
> NVRAM_SIG_FREE, We need update prev's length and checksum, then write it
> to nvram, not cur's. So lets fix this mistake now.
>
> Also use memset instead of strncpy to set the partition's name. It's
> more readable if we want to fill up with duplicate chars .
>
> Signed-off-by: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/11b7e154b132232535befe51c5
cheers
prev parent reply other threads:[~2016-09-20 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 7:30 [PATCH] powerpc/nvram: Fix an incorrect partition merge xinhui
2015-12-11 5:42 ` xinhui
2016-06-03 11:47 ` Michael Ellerman
2016-06-06 5:31 ` xinhui
2016-06-07 5:24 ` Stewart Smith
2016-06-07 11:39 ` Michael Ellerman
2016-06-13 6:40 ` xinhui
2016-09-20 13:07 ` Michael Ellerman [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=3sdjhm0b28z9t0m@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=a.hajda@samsung.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hbathini@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=xinhui.pan@linux.vnet.ibm.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).