[lkml]   [2015]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] mei, make modules.alias UUID information easier to read

On 08/29/2015 05:21 PM, Winkler, Tomas wrote:
>> Hi Prarit,
>> On Fri, Aug 28, 2015 at 07:50:52AM -0400, Prarit Bhargava wrote:
>>> Heikki, Tomas?
>> I'm afraid I don't know much about Intel's Management Engine
>> Interface. Looks like the driver is from Samuel (CC'd) so I'm guessing
>> he is the person you wanted comments from and not me.
> The patch was done against the master branch instead of char-misc-next so it doesn't apply. Anyhow I've rebased it already and I'm testing it.
> I will probably re-post it, with your permission with my other mei bus fixes.

Yep, only requires some minor adjustments in order to apply to char-misc-next.
Please repost when you can. FYI: this is needed to bring drivers/staging/unisys
out of the staging directory.

> BTW, I took the inspiration from vmbus in regards to uuid representation so it if the uuid sting hurts you, you may fix vmbus as well. I don't have any vmbus setup and I try not to fix things I cannot check.

I didn't recall other users of add_uuid() but took a look anway.

do_vmbus_entry() doesn't call add_uuid() like do_mei_entry() does. However,
the vmbus code should also just simply use add_uuid(). I can do that after
this patch gets into the kernel, as it isn't absolutely necessary to fix like
do_mei_entry(). It should be a trivial drivers/hv patch to fix all
that up.


 \ /
  Last update: 2015-09-01 02:41    [W:0.092 / U:3.996 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site