| 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
| ||
|
Message-ID: <4A029BE1.4090309@cn.fujitsu.com> Date: Thu, 07 May 2009 16:29:21 +0800 From: Yang Hongyang <yanghy@...fujitsu.com> To: Andrew Morton <akpm@...ux-foundation.org> CC: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, linux-arm-kernel@...ts.arm.linux.org.uk Subject: Re: [PATCH] remove DMA_nBIT_MASK macro Andrew Morton wrote: > On Thu, 7 May 2009 14:14:16 +0900 FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote: > >> We replaced all DMA_nBIT_MASK macros with DMA_BIT_MASK(n) but why do >> we still keep DMA_nBIT_MASK macros in include/linux/dma-mapping.h? >> >> As long as these macros exist, people use them. The current git has >> two users and linux-next have other users. >> >> Is it better to remove DMA_nBIT_MASK macros completely now? > > Yes, the plan is to remove them. > > Doing so will break lots and lots of out-of-tree drivers, causing > people some grief. Is there any way in which we can cause their use to > cause __deprecated warnings for a couple of months, to give people a > chance to migrate? > > Shall we use something like below to warn people? #define DMA_64BIT_MASK DMA_BIT_MASK(64);(__deprecated warnings:use DMA_BIT_MASK(64) instead) ? -- Regards Yang Hongyang -- 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/
Powered by blists - more mailing lists