linux-kernel - RE: [PATCH 1/1] gpio: gpio-mxs: remove the duplicated micro define

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: <74CDBE0F657A3D45AFBB94109FB122FF1740805DF4@HQMAIL01.nvidia.com>
Date:	Tue, 15 Nov 2011 10:42:16 -0800
From:	Stephen Warren <swarren@...dia.com>
To:	Dong Aisheng <dong.aisheng@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
	"arnd@...db.de" <arnd@...db.de>,
	"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
	"shawn.guo@...escale.com" <shawn.guo@...escale.com>,
	"kernel@...gutronix.de" <kernel@...gutronix.de>
Subject: RE: [PATCH 1/1] gpio: gpio-mxs: remove the duplicated micro define

Dong Aisheng wrote at Tuesday, November 15, 2011 2:55 AM:
...
> diff --git a/drivers/gpio/gpio-mxs.c b/drivers/gpio/gpio-mxs.c
...
> -#define MXS_SET		0x4
> -#define MXS_CLR		0x8

If the long-term direction on MXS is to move to gpiolib, won't MX_SET_ADDR
etc. and the inline functions that use it eventually be removed from
mach-mxs/include/mach/mxs.h hence requiring the #define be moved back
into the GPIO driver?

-- 
nvpublic

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