From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: patches added to release/test trees
Date: Thu, 22 Jun 2006 03:28:09 +0000 [thread overview]
Message-ID: <20060622032809.DCA7F3409A@koto.vergenet.net> (raw)
In-Reply-To: <200601270107.k0R17838011430@agluck-lia64.sc.intel.com>
In article <200606212319.k5LNJw7e014316@agluck-lia64.sc.intel.com> you wrote:
>
> Horms and Ian. Thanks for all the kexec patches you've posted. I'll
> be folding them in on top of the current kexec stuff soon. There
> still seem to be a lot of open issues on this, and hardly any reports
> of any testing going on. At this pace kexec/kdump will be sitting in
> "test" (and -mm) for at least another release cycle.
Hi Tony,
thanks for the feedback. I understand that kexec/kdump is quite
green/flakey and having it sit in test as you suggest is quite
approtiate in my oppinion too. Hopefully its quality can improve over
time.
As for the patches that I have sent, let me know if you need any of them
rediffed or reworked. I'm more than happy to do that kind of leg work,
as some of the patches conflict in minor ways, and some of them are
against the kdump patch before it went into your tree, and thus may need
some minor merging.
Thanks
--
Horms http://www.vergenet.net/~horms/
next prev parent reply other threads:[~2006-06-22 3:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 1:07 patches added to release/test trees Luck, Tony
2006-02-03 0:03 ` Luck, Tony
2006-02-08 23:14 ` Luck, Tony
2006-04-06 23:49 ` Luck, Tony
2006-06-21 23:19 ` Luck, Tony
2006-06-22 0:33 ` Keith Owens
2006-06-22 2:44 ` Keith Owens
2006-06-22 3:28 ` Horms [this message]
2006-06-22 17:34 ` Luck, Tony
2006-06-22 23:28 ` Keith Owens
2006-06-23 0:11 ` Andreas Schwab
2006-06-23 0:29 ` Keith Owens
2006-06-23 17:08 ` Luck, Tony
2006-06-24 8:10 ` Keith Owens
2006-06-25 22:51 ` Luck, Tony
2006-06-26 8:59 ` Horms
2006-06-26 17:23 ` Luck, Tony
2006-06-27 8:03 ` Keith Owens
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=20060622032809.DCA7F3409A@koto.vergenet.net \
--to=horms@verge.net.au \
--cc=linux-ia64@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