From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] [POWERPC] Fix rpadlpar pci hotplug driver sysfs usage
Date: Thu, 29 May 2008 21:02:17 -0700 [thread overview]
Message-ID: <200805292102.17387.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080530034134.E2D81DDEE1@ozlabs.org>
On Thursday, May 29, 2008 8:39 pm Benjamin Herrenschmidt wrote:
> When Greg "fixed" the sysfs usage of that driver a while back, he seem
> to have introduced a bug where the quotes are added around the name of
> our specific sysfs files, thus breaking the user space tool.
>
> This fixes it. Tested DLPAR operations on a POWER6 machine successfully.
Do you think this is important enough for 2.6.26?
Thanks,
Jesse
next prev parent reply other threads:[~2008-05-30 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 3:39 [PATCH] [POWERPC] Fix rpadlpar pci hotplug driver sysfs usage Benjamin Herrenschmidt
2008-05-30 4:02 ` Jesse Barnes [this message]
2008-05-30 5:45 ` Benjamin Herrenschmidt
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=200805292102.17387.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).