From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Tyrel Datwyler <turtle.in.the.kernel@gmail.com>
Cc: nfont@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 3/3] powerpc/pseries: Report in kernel device tree update to drmgr
Date: Wed, 19 Feb 2014 10:47:19 +1100 [thread overview]
Message-ID: <1392767239.25616.11.camel@pasglop> (raw)
In-Reply-To: <5303EC9E.7070507@gmail.com>
On Tue, 2014-02-18 at 15:28 -0800, Tyrel Datwyler wrote:
> In this case we get a double update which I clearly neglected to
> mention
> in the patch. The first patch in this series actually removes an
> unnecessary double update from the existing kernel implementation. The
> same information is returned by the update-nodes/properties call the
> second time around and aside from being a waste of a few cycles is
> harmless.
Thanks. Can you resend the patches with updated descriptions ? I will
try to send them to Linus by end of week.
Cheers,
Ben.
next prev parent reply other threads:[~2014-02-18 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 23:58 [PATCH v3 0/3] powerpc/pseries: fix issues in suspend/resume code Tyrel Datwyler
2014-01-31 23:58 ` [PATCH v3 1/3] powerpc/pseries: Device tree should only be updated once after suspend/migrate Tyrel Datwyler
2014-01-31 23:58 ` [PATCH v3 2/3] powerpc/pseries: Update dynamic cache nodes for suspend/resume operation Tyrel Datwyler
2014-01-31 23:58 ` [PATCH v3 3/3] powerpc/pseries: Report in kernel device tree update to drmgr Tyrel Datwyler
2014-02-17 0:22 ` Benjamin Herrenschmidt
2014-02-18 23:28 ` Tyrel Datwyler
2014-02-18 23:47 ` Benjamin Herrenschmidt [this message]
2014-02-12 21:43 ` [PATCH v3 0/3] powerpc/pseries: fix issues in suspend/resume code Tyrel Datwyler
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 20:56 [PATCH v4 " Tyrel Datwyler
2014-02-19 20:56 ` [PATCH v3 3/3] powerpc/pseries: Report in kernel device tree update to drmgr Tyrel Datwyler
2014-02-19 22:07 ` Tyrel Datwyler
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=1392767239.25616.11.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=turtle.in.the.kernel@gmail.com \
--cc=tyreld@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).