linux-kernel - Re: [PATCH 1/2] gpio-pch: cleanup _

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: <CACxGe6t2xtm-T43cBcbaqTrnPST9+R8E7dhq1rJnC+4P2__JRQ@mail.gmail.com>
Date:	Tue, 17 Jan 2012 15:49:54 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Németh Márton <nm127@...email.hu>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] gpio-pch: cleanup __iomem annotation usage

2012/1/17 Linus Walleij <linus.walleij@...aro.org>:
> 2012/1/17 Németh Márton <nm127@...email.hu>:
>
>> Hi Linux,
>
> :-)
>
> Common mistake, as are our brother Kubys who also
> appear on the lists sometimes...
>
>> You are right, the correct one should be "void __iomem *im_reg;" .
>>
>> Should I resend a patch for this?
>
> Yep just send it with subject [PATCH 1/2 v2] atleast
> that's what I usually do.

Actually, I've already applied it.  Send a follow-on patch.  It is
logically a separate change anyway since the existing code already
uses u32.

g.
--
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/