linux-kernel - Re: [PATCH 2/6] staging: vme: make [alloc|free]

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: <1312986652.11924.94.camel@Joe-Laptop>
Date:	Wed, 10 Aug 2011 07:30:52 -0700
From:	Joe Perches <joe@...ches.com>
To:	Martyn Welch <martyn.welch@...com>
Cc:	Manohar Vanga <manohar.vanga@...n.ch>, gregkh@...e.de,
	cota@...ap.org, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/6] staging: vme: make [alloc|free]_consistent bridge
 specific

On Wed, 2011-08-10 at 14:55 +0100, Martyn Welch wrote:
> On 10/08/11 14:51, Joe Perches wrote:
> > On Wed, 2011-08-10 at 14:34 +0100, Martyn Welch wrote:
> >> On 10/08/11 14:12, Joe Perches wrote:
> >>> Except for the name, those 2 blocks are identical.
> >>> Maybe create a non-pci generic version instead?
> >> I'm not sure you can (I spent quite a bit of time attempting to do just that
> >> when I wrote the original).
> > Doesn't something like this work?
[]
> Could. Though we'd have to put this in a new common file for use by
> vme_tsi148.c and vme_ca91cx42.c as the point of this was to get it out of the
> VME core code. I'm just not sure that it's worth it.

That's a bit different than what you wrote earlier.
No worries then.

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/