From: Scott Wood <scottwood@freescale.com>
To: Simon Horman <horms@verge.net.au>
Cc: <kexec@lists.infradead.org>,
Michael Ellerman <mpe@ellerman.id.au>,
<linuxppc-dev@lists.ozlabs.org>,
Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>
Subject: Re: [ANNOUNCE] kexec-tools 2.0.11-rc1
Date: Fri, 30 Oct 2015 14:45:03 -0500 [thread overview]
Message-ID: <1446234303.22185.38.camel@freescale.com> (raw)
In-Reply-To: <20151030081236.GH31252@verge.net.au>
On Fri, 2015-10-30 at 17:12 +0900, Simon Horman wrote:
> On Thu, Oct 29, 2015 at 07:23:24PM -0500, Scott Wood wrote:
> > On Fri, 2015-10-30 at 08:48 +0900, Simon Horman wrote:
> > > Hi all,
> > >
> > > I am happy to announce the release of kexec-tools 2.0.11-rc1.
> > >
> > > This is an incremental feature pre-release.
> > >
> > > So long as no serious problems arise I intend to release kexec-tools
> > > 2.0.11
> > > shortly after the release of the v4.3 kernel, which I expect to occur in
> > > the next week or so. As such testing of 2.0.11-rc1 would be greatly
> > > appreciated.
> > >
> > > I do not have any outstanding changes for 2.0.11 at this time.
> > > And I would like to only accept bug fixes at this time and take take
> > > features patches once 2.0.11 has been released.
> >
> > As I previously reported, "ppc64: purgatory: Reset primary cpu endian to
> > big-
> > endian" breaks book3e, so can http://patchwork.ozlabs.org/patch/527048/be
> > considered for this release?
>
> Yes of course, sorry for not taking more note of that.
>
> Would it be possible to get a review, e.g. from Michael?
I pinged Michael again on the original patch, and CCed him and Samuel and the
PPC list here. If they still don't respond, and you still don't want to put
the fix in without their input, then could you revert the broken patch?
-Scott
prev parent reply other threads:[~2015-10-30 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151029234849.GA28689@verge.net.au>
2015-10-30 0:23 ` [ANNOUNCE] kexec-tools 2.0.11-rc1 Scott Wood
2015-10-30 8:12 ` Simon Horman
2015-10-30 19:45 ` Scott Wood [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=1446234303.22185.38.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sam.mj@au1.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).