From: Vernon Mauery <vernon.mauery@linux.intel.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: "Mihm, James" <james.mihm@intel.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: PECI patchset status
Date: Thu, 3 Sep 2020 10:15:56 -0700 [thread overview]
Message-ID: <20200903171556.GA32795@mauery.jf.intel.com> (raw)
In-Reply-To: <20200903152753.GA57949@patrickw3-mbp.lan.stwcx.xyz>
On 03-Sep-2020 10:27 AM, Patrick Williams wrote:
>On Thu, Sep 03, 2020 at 05:57:48AM +0000, Mihm, James wrote:
>> Thank you Joel for carrying this patchset, and Intel does have an interest in getting our patchsets upstreamed.
>>
>> Since Intel has a large set of patches that need to be upstreamed our plan is to fork the kernel in github/intel-bmc and apply the intel patchsets. Upstream recipes can then pull the kernel from the intel fork with the intel patches. Intel will ensure that this fork tracks the openbmc kernel version and maintain the intel patchsets while in the process of getting them upstreamed.
>
>Rather than create a separate fork of the kernel, is there something
>that could be done here to have someone from Intel work with Joel on
>preparing the patches? When a new kernel comes out, Joel can ensure it
>works on the base AST2xxx system design and before we move all the
>systems to it, someone from Intel can rebase the non-upstreamed patches
>they are carrying? This hopefully reduces some of the burden on Joel
>and stops us from further fragmenting the community.
Keep in mind that Intel does not plan to keep the fork around
indefinitely. The hope is to fully upstream all of the patches that we
have outstanding. Our intention is not to fragment the community, but to
provide a mechanism to continue to move forward while still providing a
way for other users to build the intel-platforms target.
As an added feature, having our full kernel source in a publicly
available tree will allow us to upstream more features that depend on
kernel support that is not currently available.
--Vernon
next prev parent reply other threads:[~2020-09-03 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 8:57 PECI patchset status Joel Stanley
2020-09-03 5:57 ` Mihm, James
2020-09-03 15:27 ` Patrick Williams
2020-09-03 17:15 ` Vernon Mauery [this message]
2020-09-04 16:34 ` Patrick Williams
2020-09-08 6:04 ` Ed Tanous
2020-09-11 1:19 ` Mihm, James
2020-09-29 5:49 ` Joel Stanley
2020-10-06 17:51 ` Jae Hyun Yoo
2020-09-08 17:24 ` Public forks (Re: PECI patchset status) krtaylor
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=20200903171556.GA32795@mauery.jf.intel.com \
--to=vernon.mauery@linux.intel.com \
--cc=james.mihm@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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).