From: Michael Ellerman <mpe@ellerman.id.au>
To: Bharata B Rao <bharata.rao@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 2/2] pseries: Fix endian issues in cpu hot-removal
Date: Tue, 16 Sep 2014 17:00:23 +1000 [thread overview]
Message-ID: <1410850823.12488.4.camel@concordia> (raw)
In-Reply-To: <CAGZKiBoaXLc3dKGu5HGbU57+Lvi1KDUX=EYoi54PjYmEUjVUDg@mail.gmail.com>
On Mon, 2014-09-15 at 12:16 +0530, Bharata B Rao wrote:
> On Sat, Sep 13, 2014 at 12:41 AM, Thomas Falcon
> <tlfalcon@linux.vnet.ibm.com> wrote:
> >
> > diff --git a/arch/powerpc/platforms/pseries/dlpar.c b/arch/powerpc/platforms/pseries/dlpar.c
> > index 9e9f30b2..343dfdf 100644
> > --- a/arch/powerpc/platforms/pseries/dlpar.c
> > +++ b/arch/powerpc/platforms/pseries/dlpar.c
> > @@ -496,15 +498,15 @@ out:
> > static ssize_t dlpar_cpu_release(const char *buf, size_t count)
> > {
> > struct device_node *dn;
> > - const u32 *drc_index;
> > + const u32 drc_index;
> > int rc;
> >
> > dn = of_find_node_by_path(buf);
> > if (!dn)
> > return -EINVAL;
> >
> > - drc_index = of_get_property(dn, "ibm,my-drc-index", NULL);
> > - if (!drc_index) {
> > + rc = of_property_read_u32(dn, "ibm,my-drc-index", &drc_index);
>
> Use of const for drc_index causes compilation problems.
Yes that's clearly wrong.
Please fix and retest.
cheers
next prev parent reply other threads:[~2014-09-16 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 19:11 [PATCH v2 1/2] pseries: Fix endian issues in onlining cpu threads Thomas Falcon
2014-09-12 19:11 ` [PATCH v2 2/2] pseries: Fix endian issues in cpu hot-removal Thomas Falcon
2014-09-15 6:46 ` Bharata B Rao
2014-09-16 7:00 ` Michael Ellerman [this message]
2014-09-15 3:01 ` [PATCH v2 1/2] pseries: Fix endian issues in onlining cpu threads Michael Ellerman
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=1410850823.12488.4.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=bharata.rao@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tlfalcon@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).