From: "Michael Ellerman" <michael@ellerman.id.au>
To: "Santiago Leon" <santil@us.ibm.com>
Cc: linuxppc64-dev@ozlabs.org, jgarzik@pobox.com, anton@samba.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec
Date: Tue, 29 Aug 2006 22:58:02 +1000 [thread overview]
Message-ID: <dc1166600608290558o4c25651cud82d2217a6a0fb61@mail.gmail.com> (raw)
In-Reply-To: <4452724D.7050800@us.ibm.com>
On 4/29/06, Santiago Leon <santil@us.ibm.com> wrote:
> Michael Ellerman wrote:
> > Any chance of getting it into to 2.6.17 ...
2.6.19 perhaps?
cheers
next prev parent reply other threads:[~2006-08-29 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060131041055.5623C68A46@ozlabs.org>
[not found] ` <20060131042903.GF28896@krispykreme>
[not found] ` <44074A22.8060705@us.ibm.com>
2006-03-27 1:11 ` [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec Michael Ellerman
2006-04-26 10:37 ` Michael Ellerman
2006-04-28 19:51 ` Santiago Leon
2006-08-29 12:58 ` Michael Ellerman [this message]
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=dc1166600608290558o4c25651cud82d2217a6a0fb61@mail.gmail.com \
--to=michael@ellerman.id.au \
--cc=anton@samba.org \
--cc=jgarzik@pobox.com \
--cc=linuxppc64-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=santil@us.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).