From: Michael Ellerman <michael@ellerman.id.au>
To: jgarzik@pobox.com
Cc: linuxppc64-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec
Date: Mon, 27 Mar 2006 12:11:16 +1100 [thread overview]
Message-ID: <1143421876.7795.2.camel@localhost.localdomain> (raw)
In-Reply-To: <44074A22.8060705@us.ibm.com>
On Thu, 2006-03-02 at 13:40 -0600, Santiago Leon wrote:
> From: Michael Ellerman <michael@ellerman.id.au>
>
> After a kexec the veth driver will fail when trying to register with the
> Hypervisor because the previous kernel has not unregistered.
>
> So if the registration fails, we unregister and then try again.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> Acked-by: Anton Blanchard <anton@samba.org>
> Signed-off-by: Santiago Leon <santil@us.ibm.com>
> ---
>
> drivers/net/ibmveth.c | 32 ++++++++++++++++++++++++++------
> 1 files changed, 26 insertions(+), 6 deletions(-)
Looks like this hit the floor. Any chance of getting it into to 2.6.17
Jeff? AFAICT it should still apply cleanly.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
next prev parent reply other threads:[~2006-03-27 1:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060131041055.5623C68A46@ozlabs.org>
[not found] ` <20060131042903.GF28896@krispykreme>
2006-03-02 19:40 ` [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec Santiago Leon
2006-03-03 0:22 ` Michael Ellerman
2006-03-03 0:34 ` Randy.Dunlap
2006-03-03 1:00 ` Paul Mackerras
2006-03-03 1:10 ` Michael Ellerman
2006-03-03 4:12 ` Randy.Dunlap
2006-03-03 1:04 ` Jeff Garzik
2006-03-03 2:11 ` Michael Ellerman
2006-03-27 1:11 ` Michael Ellerman [this message]
2006-04-26 10:37 ` Michael Ellerman
2006-04-28 19:51 ` Santiago Leon
2006-08-29 12:58 ` Michael Ellerman
2006-09-18 4:31 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=1143421876.7795.2.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=jgarzik@pobox.com \
--cc=linuxppc64-dev@ozlabs.org \
--cc=netdev@vger.kernel.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).