[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CB9F11E856CFD04BB18EC1C68F2598931B11F2@NTXXIAMBX01.xacn.micron.com>
Date: Fri, 25 Jul 2014 02:29:18 +0000
From: bpqw <bpqw@...ron.com>
To: Brian Norris <computersforpeace@...il.com>,
"Gupta, Pekon" <pekon@...com>
CC: bpqw <bpqw@...ron.com>, "ron@...ian.org" <ron@...ian.org>,
"artem.bityutskiy@...ux.intel.com" <artem.bityutskiy@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"b32955@...escale.com" <b32955@...escale.com>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"ezequiel.garcia@...e-electrons.com"
<ezequiel.garcia@...e-electrons.com>,
"u.kleine-koenig@...gutronix.de" <u.kleine-koenig@...gutronix.de>,
"dwmw2@...radead.org" <dwmw2@...radead.org>
Subject: RE: Subject: [PATCH 1/1] mtd:nand:fix nand_lock/unlock() function
>OK, I won't drop them yet.
>As you note, there's no user-space support. There's actually no one using them even in the kernel, which is why I considered dropping them.
>If you want to use them, find a proper way to use them then! (I'm not
>sure: do they match with mtd_lock() / ioctl(MEMLOCK) interface?)
How about my patch, Do you think there is any other need to change?
White
--
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