From: Ed Tanous <edtanous@google.com>
To: Lei Yu <yulei.sh@bytedance.com>
Cc: openbmc <openbmc@lists.ozlabs.org>,
Thang Nguyen <thang@amperemail.onmicrosoft.com>
Subject: Re: [External] Re: New test for patches in openbmc/openbmc
Date: Mon, 27 Sep 2021 09:33:47 -0700 [thread overview]
Message-ID: <CAH2-KxBpQbmBAedd63-1KORd9Z81D-gWM7oqQPU05Q=4S5XYzQ@mail.gmail.com> (raw)
In-Reply-To: <CAGm54UGjh9QTAw_mPdPCpZ7WihTHYXRe0m=xCWrPmpvDb99p3Q@mail.gmail.com>
On Fri, Sep 24, 2021 at 4:06 AM Lei Yu <yulei.sh@bytedance.com> wrote:
>
> On Fri, Sep 24, 2021 at 6:29 PM Thang Nguyen
> <thang@amperemail.onmicrosoft.com> wrote:
> >
> > Hi Ed,
> > I have 2 questions on this topics:
> > 1. I have a patch
> > meta-ampere/meta-jade/recipes-bsp/u-boot/u-boot-aspeed/0003-aspeed-support-passing-system-reset-status-to-kernel.patch
> > which ported from Intel code. It is to add BMC reset cause to boot
> > command line (/proc/cmdline) in which I can check for chassis power
> > policy which skip when BMC reboots (does not change CPU status). As the
> > patch is from Intel, what is the procedure to make it reviewed and
> > applied to u-boot?
> >
>
> I have a similar case.
> As an x86 system, some of the recipes/changes are referenced from
> Intel-BMC, which is not upstreamed.
> Currently, we had patches related to UART routing and
> phosphor-node-manager-proxy.
> The UART routing patches are being upstreamed thanks to Troy.
> The change to node-manager is related to the HW design difference, and
> due to the fact that phosphor-node-manager-proxy is in Intel-BMC, we
> can not really make the patch upstream.
I'm not following why that's preventing upstreaming. If
node-manager-proxy is something you need on your systems, I don't see
a reason why we would avoid cleaning it up and upstreaming it, but I
have no details on what this patch is, or what it does, so it's really
hard to talk in concrete terms about how to proceed next.
>
> How do we handle such cases?
>
> --
> BRs,
> Lei YU
next prev parent reply other threads:[~2021-09-27 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 22:35 New test for patches in openbmc/openbmc Ed Tanous
2021-09-22 9:02 ` Alexander Amelkin
2021-09-22 13:15 ` Verdun, Jean-Marie
2021-09-22 23:35 ` Oskar Senft
2021-09-23 2:49 ` John Broadbent
2021-09-23 17:09 ` Benjamin Fair
2021-09-23 23:57 ` Ed Tanous
2021-09-23 23:38 ` Ed Tanous
2021-09-24 10:28 ` Thang Nguyen
2021-09-24 11:06 ` [External] " Lei Yu
2021-09-27 16:33 ` Ed Tanous [this message]
2021-09-28 8:36 ` Lei Yu
2021-10-08 8:32 ` Lei YU
2021-10-08 17:35 ` Ed Tanous
2021-10-09 2:18 ` Lei Yu
2021-10-11 17:47 ` Ed Tanous
2021-09-27 16:39 ` Ed Tanous
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='CAH2-KxBpQbmBAedd63-1KORd9Z81D-gWM7oqQPU05Q=4S5XYzQ@mail.gmail.com' \
--to=edtanous@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=thang@amperemail.onmicrosoft.com \
--cc=yulei.sh@bytedance.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).