linux-kernel - Re: [git patches] libata hibernation fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49739371.5030107@garzik.org>
Date:	Sun, 18 Jan 2009 15:39:13 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Frans Pop <elendil@...net.nl>, tj@...nel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git patches] libata hibernation fixes

Rafael J. Wysocki wrote:
> On Sunday 18 January 2009, Frans Pop wrote:
>> Rafael J. Wysocki wrote:
>>> There is a name conflict with a change applied after this patchset had
>>> been created.  The appended patch fixes it for me.
>> [...]
>>> @@ -483,7 +483,7 @@ const struct dmi_system_id *dmi_first_match(const struct dmi_system_id *list)
>>>         const struct dmi_system_id *d; 
>>>
>>>         for (d = list; d->ident; d++)
>>> -               if (dmi_match(d))
>>> +               if (dmi_matches(d))
>>>                         return d;
>> I get two warnings when compiling your patch with this correction on top:
> 
> Hm, there were more patches than one, so I'm not sure.  When I apply all of
> them, I don't see these error, but perhaps I should resend the entire series.
> Will do tomorrow.

That would be useful...  I was planning to regenerate the series, but 
this would save time.

Thanks!

	Jeff




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/