[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/5] ipmi: Add support to customize OEM functions
|
From: |
Cédric Le Goater |
|
Subject: |
Re: [PATCH 2/5] ipmi: Add support to customize OEM functions |
|
Date: |
Thu, 7 Nov 2019 18:29:18 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 |
On 07/11/2019 18:25, Corey Minyard wrote:
> On Thu, Nov 07, 2019 at 06:14:58PM +0100, Cédric Le Goater wrote:
>>>>> What's the plan for merging this, once it's ready? Is there an IPMI
>>>>> tree for it to be staged in? If not I could take it through the ppc
>>>>> tree, but I'd need some Acked-bys in that case.
>>>>
>>>> I have an IPMI tree for this. I was assuming it was going in to the PPC
>>>> tree, but it's not big deal.
>>>
>>> I'd be more comfortable if the generic ipmi changes went through the
>>> ipmi tree.
>>
>> Here is the patch :
>>
>> http://patchwork.ozlabs.org/patch/1185187/
>
> Ok, I have this in my tree.
>
> I assume there is nothing like the linux-next tree for qemu, right?
no. These IPMI OEM commands are handled by the OPAL firmware only.
C.