From: "Norman James" <njames@us.ibm.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Patches <openbmc-patches@stwcx.xyz>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH openbmc] Update recipes to pick changes for Foxconn build
Date: Mon, 1 Feb 2016 20:25:17 -0600 [thread overview]
Message-ID: <201602020225.u122PSug016677@d01av03.pok.ibm.com> (raw)
In-Reply-To: <CACPK8XcEhamUF3vC2cgb-a4Kwi2DGpn5FZVpcnM-GN7i3Gd-XQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2001 bytes --]
When are you doing a release? OCC is broken in current kernel release.
Regards,
Norman James
IBM - POWER Systems Architect
Phone: 1-512-286-6807 (T/L: 363-6807)
Internet: njames@us.ibm.com
From: Joel Stanley <joel@jms.id.au>
To: OpenBMC Patches <openbmc-patches@stwcx.xyz>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Date: 02/01/2016 07:13 PM
Subject: Re: [PATCH openbmc] Update recipes to pick changes for Foxconn
build
Sent by: "openbmc" <openbmc-bounces+njames=us.ibm.com@lists.ozlabs.org>
On Tue, Feb 2, 2016 at 10:30 AM, OpenBMC Patches
<openbmc-patches@stwcx.xyz> wrote:
> From: Adriana Kobylak <anoo@us.ibm.com>
>
> Update recipes to pick up changes required for Foxconn delivery
> ---
> meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.3.bb | 2
+-
> meta-phosphor/common/recipes-phosphor/host-ipmid/host-ipmid-fru.bb | 2
+-
> meta-phosphor/common/recipes-phosphor/host-ipmid/host-ipmid.bb | 2
+-
> meta-phosphor/common/recipes-phosphor/settings/settings.bb | 2
+-
> meta-phosphor/common/recipes-phosphor/skeleton/skeleton.bb | 2
+-
> 5 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.3.bb
b/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.3.bb
> index 3b1eec8..13887e6 100644
> --- a/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.3.bb
> +++ b/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.3.bb
> @@ -10,7 +10,7 @@ SRC_URI =
"git://github.com/openbmc/linux;protocol=git;branch=${KBRANCH}"
> LINUX_VERSION ?= "4.3"
> LINUX_VERSION_EXTENSION ?= "-${SRCREV}"
>
> -SRCREV="openbmc-20160127-1"
> +SRCREV="7fbee5252ddea512c208727377de7df5968ee8f1"
This is not how we do the kernel releases. Please do not merge this.
Regards,
Joel
_______________________________________________
openbmc mailing list
openbmc@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/openbmc
[-- Attachment #1.2: Type: text/html, Size: 3341 bytes --]
[-- Attachment #2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]
next prev parent reply other threads:[~2016-02-02 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:00 [PATCH openbmc] Update recipes to pick changes for Foxconn build OpenBMC Patches
2016-02-02 0:00 ` OpenBMC Patches
2016-02-02 1:09 ` Joel Stanley
2016-02-02 2:25 ` Norman James [this message]
[not found] ` <201602020225.u122PS5J020332@d03av03.boulder.ibm.com>
2016-02-02 2:33 ` Joel Stanley
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=201602020225.u122PSug016677@d01av03.pok.ibm.com \
--to=njames@us.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc-patches@stwcx.xyz \
--cc=openbmc@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.