From: Joel Stanley <joel@jms.id.au>
To: "Mihm, James" <james.mihm@intel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Vernon Mauery <vernon.mauery@linux.intel.com>
Subject: Re: PECI patchset status
Date: Tue, 29 Sep 2020 05:49:27 +0000 [thread overview]
Message-ID: <CACPK8XeXm4_JP-pt9OzcHQwA2sqpHMVnW1kpNUQRh+ULRmG-Cw@mail.gmail.com> (raw)
In-Reply-To: <DM5PR11MB188420C2AF67DA8C09C4689F90240@DM5PR11MB1884.namprd11.prod.outlook.com>
On Fri, 11 Sep 2020 at 01:20, Mihm, James <james.mihm@intel.com> wrote:
> Would it be acceptable for all of the 84+ Intel patches to reside in the openbmc repo while we work through the upstreaming process?
> Some of the patches require design changes and will take much longer to upstream.
This is the intent of the openbmc tree. THe patches need to be posted,
in reviewable series, to be included.
As discussed in this thread regarding the PECI patches, they have been
around for a long time without submission. They will need to be posted
upstream again before I put them in the OpenBMC tree.
Early September, when this thread was started, was a great time to
make the PECI submission in terms of the upstream kernel development
cycle. The next best time is now.
Cheers,
Joel
next prev parent reply other threads:[~2020-09-29 5:51 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
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 [this message]
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=CACPK8XeXm4_JP-pt9OzcHQwA2sqpHMVnW1kpNUQRh+ULRmG-Cw@mail.gmail.com \
--to=joel@jms.id.au \
--cc=james.mihm@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@linux.intel.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).