From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Zev Weiss <zev@bewilderbeest.net>, openbmc@lists.ozlabs.org
Cc: Jason M Biils <jason.m.bills@linux.intel.com>,
James Feist <james.feist@linux.intel.com>
Subject: Re: [PATCH 0/2] PECI patchset tweaks
Date: Mon, 28 Sep 2020 12:01:05 -0700 [thread overview]
Message-ID: <4d313c8c-7f73-8e45-1480-9497be6df400@linux.intel.com> (raw)
In-Reply-To: <20200926212734.23836-1-zev@bewilderbeest.net>
Hello Zev,
On 9/26/2020 2:27 PM, Zev Weiss wrote:
> [Re-sending as I clumsily typoed the mailing list's address on the
> first attempt; apologies for the duplication.]
>
> Hello,
>
> These patches address a few small things I noticed with the PECI patch
> set currently in the OpenBMC kernel tree. Assuming they're deemed
> acceptable, I'd of course hope they get folded in to the version of
> the PECI code that gets upstreamed into the mainline kernel.
>
> (Please let me know if there's some other way I should send this -- I
> looked for but couldn't find a gerrit repo for the obmc kernel or any
> kernel-specific patch submission instructions in
> openbmc/docs/CONTRIBUTING.md, so 'git send-email' is my best guess.)
This mailing list would be a right place as long as the PECI patch set
is in OpenBMC kernel tree but in case if it is removed from the tree
later (probably from the 5.9 kernel), you may need to use pull request
through https://github.com/Intel-BMC/openbmc when it replaces the
kernel repo with forked kernel.
Thanks,
Jae
>
> Thanks,
> Zev
>
>
prev parent reply other threads:[~2020-09-28 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 21:27 [PATCH 0/2] PECI patchset tweaks Zev Weiss
2020-09-26 21:27 ` [PATCH 1/2] peci: fix error-handling in peci_dev_ioctl() Zev Weiss
2020-09-28 19:03 ` Jae Hyun Yoo
2020-09-28 19:09 ` Zev Weiss
2020-09-28 19:37 ` Jae Hyun Yoo
2020-09-29 5:55 ` Joel Stanley
2020-09-26 21:27 ` [PATCH 2/2] peci-cputemp: label CPU cores from zero instead of one Zev Weiss
2020-09-28 19:08 ` Jae Hyun Yoo
2020-09-28 19:54 ` Zev Weiss
2020-09-28 20:21 ` Jae Hyun Yoo
2020-09-28 21:09 ` Zev Weiss
2020-09-28 21:32 ` Jae Hyun Yoo
2020-09-28 22:02 ` Zev Weiss
2020-09-28 22:20 ` Jae Hyun Yoo
2020-09-29 6:00 ` Joel Stanley
2020-10-06 18:01 ` Jae Hyun Yoo
2020-10-07 5:39 ` Joel Stanley
2020-09-28 19:01 ` Jae Hyun Yoo [this message]
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=4d313c8c-7f73-8e45-1480-9497be6df400@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=james.feist@linux.intel.com \
--cc=jason.m.bills@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=zev@bewilderbeest.net \
/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).