From: John Rose <johnrose@austin.ibm.com>
To: Al Viro <viro@ftp.linux.org.uk>, Greg KH <greg@kroah.com>,
michael@ellerman.id.au, Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [viro@ftp.linux.org.uk: [PATCH] rpadlpar breakage - fallout of struct subsystem removal]
Date: Wed, 16 May 2007 16:22:37 -0500 [thread overview]
Message-ID: <1179350557.14199.10.camel@sinatra.austin.ibm.com> (raw)
In-Reply-To: <20070515194729.GE4095@ftp.linux.org.uk>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Verified boot, hotplug, and dynamic add/remove of buses. Perfect,
thanks Al!
Acked-by: John Rose <johnrose@austin.ibm.com>
prev parent reply other threads:[~2007-05-16 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 19:47 [viro@ftp.linux.org.uk: [PATCH] rpadlpar breakage - fallout of struct subsystem removal] Al Viro
2007-05-16 0:49 ` Michael Ellerman
2007-05-16 6:57 ` Benjamin Herrenschmidt
2007-05-16 7:15 ` Greg KH
2007-05-16 21:22 ` John Rose [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=1179350557.14199.10.camel@sinatra.austin.ibm.com \
--to=johnrose@austin.ibm.com \
--cc=greg@kroah.com \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=viro@ftp.linux.org.uk \
/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).