From: "Mihm, James" <james.mihm@intel.com>
To: Joel Stanley <joel@jms.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: RE: PECI patchset status
Date: Thu, 3 Sep 2020 05:57:48 +0000 [thread overview]
Message-ID: <DM5PR11MB188419A3302F33CE6FE80740902C0@DM5PR11MB1884.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACPK8XddFvszC1daDKTtqwkE-XDfB7uYFP_H4HZXNUxvNHUaqw@mail.gmail.com>
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.
Thanks, James.
-----Original Message-----
From: openbmc <openbmc-bounces+james.mihm=intel.com@lists.ozlabs.org> On Behalf Of Joel Stanley
Sent: Monday, August 31, 2020 1:57 AM
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: PECI patchset status
Hello OpenBMCers,
The PECI patchset has been carried in the openbmc tree in some form
since it was first posted in December 2017.
It has not made it upstream in that time, placing the maintenance
burden on me as the kernel maintainer. Generally this isn't a large
amount of work, although in some cases it has held up releasing kernel
branches. Today I noticed that the icotl number it chose has been
claimed by a different ioctl in linux-next, meaning we are guaranteed
to have future kernel/userspace incompatibility.
OpenBMC has strong rules about upstreaming kernel patches, and in
particular userspace facing code, to avoid this issue.
Given the lack of progress I propose dropping it from the OpenBMC
kernel tree until it is merged upstream. This would necessitate
removing tiogapass from the OpenBMC CI, as it relies on PECI support
in the kernel to build.
If you have an interest in the patchset staying in openbmc, we would
need someone (or a team) to take the patchset (v11 is the latest[1])
and submit for inclusion in the mainline kernel, including an entry in
MAINTAINERS to commit to future maintenance. Now is the perfect time
to submit for inclusion in 5.10.
[1] https://lore.kernel.org/linux-hwmon/20191211194624.2872-1-jae.hyun.yoo@linux.intel.com/
Cheers,
Joel
next prev parent reply other threads:[~2020-09-03 5:57 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 [this message]
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
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=DM5PR11MB188419A3302F33CE6FE80740902C0@DM5PR11MB1884.namprd11.prod.outlook.com \
--to=james.mihm@intel.com \
--cc=joel@jms.id.au \
--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.