From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Patrick Williams <patrick@stwcx.xyz>, Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
OpenBMC Patches <openbmc-patches@stwcx.xyz>,
skiboot list <skiboot@lists.ozlabs.org>
Subject: Re: [PATCH openbmc 3/3] meta-openpower: Update pflash version
Date: Tue, 12 Jul 2016 11:39:59 +1000 [thread overview]
Message-ID: <87a8hnskgg.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160711215731.GB12483@asimov.austin.ibm.com>
Patrick Williams <patrick@stwcx.xyz> writes:
> Stewart,
>
> Bump. Didn't see a reply from you on this.
Thanks, I somehow missed it.
> On Fri, Jul 01, 2016 at 10:23:24AM +0930, Joel Stanley wrote:
>> On Fri, Jul 1, 2016 at 6:57 AM, Patrick Williams <patrick@stwcx.xyz> wrote:
>> > On Thu, Jun 30, 2016 at 11:20:33AM -0500, OpenBMC Patches wrote:
>> >> From: Joel Stanley <joel@jms.id.au>
>> >>
>> >> Move to HEAD so we can drop the patches we carry.
>> >>
>> >> Signed-off-by: Joel Stanley <joel@jms.id.au>
>> >
>> > Stewart released 5.2.3 with these fixes. Can you put us onto that
>> > instead? Prefer to stay on a released version rather than a commit.
>>
>> It was my intention to bump us to 5.2.3. However, I went and looked at
>> the recipe and we were carrying 7 patches against skiboot. Only the
>> 7th is on the stable branch.
>>
>> Stewart,
>>
>> I assume you don't want to tag master at all?
>>
>> If not, can you please pull this list of commits into the stable branch:
>>
>> e42206bf0729782330778e77283af2aca23499dc
>> 7c7911eb7bea505474c3062bf5b0c60d99b502a5
>> e5fc583e610d4360f8fe50f225c868cb3019c1a7
>> e415b3b9bf0441745f442e12bfce25ed49c589bf
>> 45e548176e16ad8ba9540fcd75131ba4993e42b7
>> 24ae270984a37525f8393eeccbd0ac55da4503e1
>>
>> They are all related to building pflash.
Done. Also cherry picked 2ebc0ae0a2c61c006062ba42fc253296060c34cf as it
had Fixes:e42206bf0729782330778e77283af2aca23499dc in it.
I can tag a 5.2.4 with these bits in it today if you like too.
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2016-07-12 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 16:20 [PATCH openbmc 0/3] Fixes for witherspoon kernel, pflash and skeleton OpenBMC Patches
2016-06-30 16:20 ` [PATCH openbmc 1/3] witherspoon: bump kernel revision OpenBMC Patches
2016-06-30 16:20 ` [PATCH openbmc 2/3] meta-phosphor: Bump skeleton revision OpenBMC Patches
2016-06-30 16:20 ` [PATCH openbmc 3/3] meta-openpower: Update pflash version OpenBMC Patches
2016-06-30 21:27 ` Patrick Williams
2016-07-01 0:53 ` Joel Stanley
2016-07-11 21:57 ` Patrick Williams
2016-07-12 1:39 ` Stewart Smith [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=87a8hnskgg.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc-patches@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=skiboot@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.