linux-kernel - Re: [TRIVIAL PATCH v2] treewide: Convert uses of struct resource to resource

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: <1307635784.13329.4.camel@Joe-Laptop>
Date:	Thu, 09 Jun 2011 09:09:44 -0700
From:	Joe Perches <joe@...ches.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	H Hartley Sweeten <hartleys@...ionengravers.com>
Subject: Re: [TRIVIAL PATCH v2] treewide: Convert uses of struct resource
 to resource_size(ptr)

On Thu, 2011-06-09 at 14:25 +0200, Jiri Kosina wrote:
> On Tue, 7 Jun 2011, Joe Perches wrote:
> > Several fixes as well where the +1 was missing.
> > Done via coccinelle scripts like:
> > @@
> > struct resource *ptr;
> > @@
> > - ptr->end - ptr->start + 1
> > + resource_size(ptr)
> > and some grep and typing.
> > Mostly uncompiled, no cross-compilers.
> > Some checkpatch complaints cheerfully ignored.
> > Signed-off-by: Joe Perches <joe@...ches.com>
> thanks a lot for the patch. I will be happily taking it. However it seems 
> like some of the files are going away/have been moved in -next. Could you 
> please respin on top of what is still applicable on -next and resend? 

Hi Jiri.

The original patch is for next-20110607.
There were 2 identical patches for resource_size
applied to the next tree as of next-20110609.

I just cherry-pick'ed it and the diff is the same
modulo those 2 already applied bits.

Because it's pretty large, I'll send the new diff
just to you off-list.

cheers, Joe

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