From: Corey Minyard <minyard@acm.org>
To: Phil Pokorny <ppokorny@penguincomputing.com>,
openipmi-developer@lists.sourceforge.net,
linux-i2c@vger.kernel.org
Subject: Re: Please pick up i2c-xlp9xx driver patches
Date: Wed, 31 Jan 2018 15:41:15 -0600 [thread overview]
Message-ID: <2dc0cbda-2e49-7e10-c619-c69fb4aef061@acm.org> (raw)
In-Reply-To: <CAAek22EEs_mHcKg80Ei=FRNH88KVjWJNHHVZ3cU204c0fW8v2w@mail.gmail.com>
On 01/31/2018 03:06 PM, Phil Pokorny wrote:
> Cross-posting to openipmi and linux-i2c... (in plain text this time...
> my apologies.)
> There are four patches from Cavium starting with
> https://lkml.org/lkml/2018/1/18/12 that fix an issue with the xlp9xx
> driver that causes ipmi_ssif not to be able to detect a platform BMC.
>
> I have two different pre-production hardware chassis that are affected
> by this issue and I don't see that the patches were included in v4.15.
>
> I wonder if either Corey or Jean could/should pick these up and submit
> upstream?
It is all I2C changes, so it's outside my realm.
-corey
> There doesn't seem to be a MAINTAINERS entry for the
> i2c-xlp9xx The driver was submitted Cavium (was Broadcom at the time)
> The posts don't seem to have gotten any comments on LKML.
>
> I tested the patches and they fix the ipmi_ssif detection issue I had.
> So I'm willing to add "Tested-by" to the patches if that helps.
>
> Would like to see these patches make it up-stream so I can they ask
> that they be included in the Red Hat and SuSE distro kernels for
> ARM64.
>
> Thanks,
> Phil P.
>
> --
> Philip Pokorny, RHCE
> Chief Technology Officer
> PENGUIN COMPUTING, Inc
> www.penguincomputing.com
>
> Changing the world through technical innovation
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Openipmi-developer mailing list
> Openipmi-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-01-31 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 21:01 Please pick up i2c-xlp9xx driver patches Phil Pokorny
2018-01-31 21:06 ` Phil Pokorny
2018-01-31 21:41 ` Corey Minyard [this message]
2018-02-01 8:12 ` Wolfram Sang
2018-02-02 6:24 ` Phil Pokorny
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=2dc0cbda-2e49-7e10-c619-c69fb4aef061@acm.org \
--to=minyard@acm.org \
--cc=linux-i2c@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=ppokorny@penguincomputing.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