All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Dropping PECI patches
Date: Mon, 2 Dec 2019 10:09:30 -0800	[thread overview]
Message-ID: <be709e4f-1215-3d88-9974-1989b9867e60@linux.intel.com> (raw)
In-Reply-To: <CACPK8XffZqTq3YqEEcA7mm4d1k0V30o1TLE79nBOGrVcEBCjog@mail.gmail.com>

Hi Joel,

Thanks for letting me know this. Also, thanks a lot for carrying the
out-of-tree PECI patches in OpenBMC kernel tree so far.

Can I submit updated PECI patches to OpenBMC upstream if I'm gonna add
it back? Linux upstreaming isn't ready yet because configfs support
should be implemented to address subsystem maintainer's comments but it
needs at this moment in OpenBMC kernel tree to keep developing
dbus-sensors support.

Thanks,
Jae

On 12/1/2019 8:35 PM, Joel Stanley wrote:
> Hi Jae,
> 
> As I have not seen an upstream submission of PECI for a number of
> release cycles (since January, over 10 months ago) it will be dropped
> from the OpenBMC kernel tree.
> 
> If you still want this code in the kernel you will need to make a new
> upstream submission.
> 
> This aligns with the OpenBMC kernel development process, where a patch
> is carried to assist developers who are actively working to get their
> drivers merged upstream
> 
> Cheers,
> 
> Joel
> 

  reply	other threads:[~2019-12-02 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  4:35 Dropping PECI patches Joel Stanley
2019-12-02 18:09 ` Jae Hyun Yoo [this message]
2019-12-02 21:54   ` Joel Stanley
2019-12-03  1:25     ` Jae Hyun Yoo
2019-12-03  2:47       ` Joel Stanley
2019-12-04 18:00         ` Jae Hyun Yoo

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=be709e4f-1215-3d88-9974-1989b9867e60@linux.intel.com \
    --to=jae.hyun.yoo@linux.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.