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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070721202637.8895b426.sfr@canb.auug.org.au>
Date:	Sat, 21 Jul 2007 20:26:37 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: CONFIG_VIRT_TO_BUS: what about bus_to_virt?

On Sat, 21 Jul 2007 11:52:18 +0200 Stefan Richter <stefanr@...6.in-berlin.de> wrote:
>
> Is it sensible and safe to let a driver which uses bus_to_virt (but not
> virt_to_bus) depend on CONFIG_VIRT_TO_BUS?

If a driver depends on either bus_to_virt or virt_to_bus, then it
depend on CONFIG_VIRT_TO_BUS.  The intention is to exclude the driver from
being built on achitectures that don't implement those primitives (and
architectures always implement them both or neither).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ