From: Joel Stanley <joel@jms.id.au>
To: Patrick Williams <patrick@stwcx.xyz>,
Timothy Pearson <tpearson@raptorengineering.com>
Cc: Matt Spinler <mspinler@linux.vnet.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: I2C device driver names
Date: Mon, 10 Oct 2016 12:57:47 +1100 [thread overview]
Message-ID: <CACPK8Xfwj82abqJS_j20WZFzwwPZke2y1FCHk3eoMTwJopxDpw@mail.gmail.com> (raw)
In-Reply-To: <20161007015152.GA17914@heinlein.lan>
On Fri, Oct 7, 2016 at 12:51 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
> On Fri, Oct 07, 2016 at 10:42:24AM +1100, Joel Stanley wrote:
>> > PMBus Power supplies: ?
>> >
>> > MAX31785 fan controller: max,max31785
>>
>> Doesn't appear to be an upstream driver. Please open a ticket.
>
> Timothy @ Raptor wrote a driver for this recently, didn't he? Joel, I
> thought you were going to merge it in for the time being. Timothy
Yeah. I did ask that he spit out the maintainers part of that patch
before we applied it.
Timothy, are you able to make that change?
> mentioned that there was some upstream work going on in that subsystem
> that was preventing it from be merged in the current state but that the
> subsystem owner was likely going to take it on.
Timothy, do you have any update on the rewrite?
Cheers,
Joel
>
> https://patchwork.ozlabs.org/patch/672045/
>
> --
> Patrick Williams
next prev parent reply other threads:[~2016-10-10 1:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 20:14 I2C device driver names Matt Spinler
2016-10-06 23:42 ` Joel Stanley
2016-10-07 1:51 ` Patrick Williams
2016-10-10 1:57 ` Joel Stanley [this message]
2016-10-11 14:41 ` Timothy Pearson
2016-10-11 23:11 ` Joel Stanley
2016-10-12 15:31 ` Timothy Pearson
2016-10-07 0:24 ` Milton Miller II
2016-10-07 20:08 ` Matt Spinler
2016-10-18 18:26 ` Matt Spinler
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=CACPK8Xfwj82abqJS_j20WZFzwwPZke2y1FCHk3eoMTwJopxDpw@mail.gmail.com \
--to=joel@jms.id.au \
--cc=mspinler@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=tpearson@raptorengineering.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 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.