From: Corey Minyard <minyard@acm.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jean Delvare <jdelvare@suse.de>,
Andy Lutomirski <luto@kernel.org>,
Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH 2/4] dmi: Add a DMI firmware node and handling
Date: Sun, 31 Jan 2016 18:36:37 -0600 [thread overview]
Message-ID: <56AEA895.5050704@acm.org> (raw)
In-Reply-To: <CALCETrVrOxQc1_qaYsa-rPMNYs4vdiFBgULqp2K7VTL1j=Qhvg@mail.gmail.com>
On 01/31/2016 04:46 PM, Andy Lutomirski wrote:
> On Fri, Jan 29, 2016 at 2:43 PM, <minyard@acm.org> wrote:
>> From: Corey Minyard <cminyard@mvista.com>
>>
>> This is so that an IPMI platform device can be created from a
>> DMI firmware entry.
> This doesn't apply for me. What's it based on?
>
> --Andy
It was off of Linus' master a couple of days ago. I just rebased to the
latest and it applied cleanly.
I can resend, if you like.
Thanks,
-corey
next prev parent reply other threads:[~2016-02-01 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 22:43 [PATCH 0/4] dmi: Rework to get IPMI autoloading from DMI tables minyard
2016-01-29 22:43 ` [PATCH 1/4] dmi: remove const from return of dmi_find_device minyard
2016-01-29 22:43 ` [PATCH 2/4] dmi: Add a DMI firmware node and handling minyard
2016-01-29 23:59 ` kbuild test robot
2016-01-30 0:35 ` Corey Minyard
2016-01-30 0:41 ` kbuild test robot
2016-01-31 22:46 ` Andy Lutomirski
2016-02-01 0:36 ` Corey Minyard [this message]
2016-02-01 9:25 ` Jean Delvare
2016-02-02 13:37 ` Corey Minyard
2016-02-02 18:25 ` Andy Lutomirski
2016-02-03 16:51 ` Corey Minyard
2016-01-29 22:43 ` [PATCH 3/4] dmi: Move IPMI DMI scanning to the DMI code minyard
2016-01-29 22:43 ` [PATCH 4/4] dmi/ipmi: Add IPMI DMI devices as platform devices minyard
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=56AEA895.5050704@acm.org \
--to=minyard@acm.org \
--cc=cminyard@mvista.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=openipmi-developer@lists.sourceforge.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).