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
| ||
|
Date: Sun, 21 Sep 2014 12:27:27 +0300 From: Boaz Harrosh <boaz@...xistor.com> To: Dan Williams <dan.j.williams@...el.com>, Jeff Moyer <jmoyer@...hat.com> CC: Boaz Harrosh <openosd@...il.com>, Ross Zwisler <ross.zwisler@...ux.intel.com>, Jens Axboe <axboe@...nel.dk>, Matthew Wilcox <matthew.r.wilcox@...el.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-nvdimm@...1.01.org Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent memory driver On 09/19/2014 07:27 PM, Dan Williams wrote: > before adding any new device > discovery capabilities to pmem. > I lost you? what "new device discovery capabilities" do you see in Ross's or my code to pmem? Actually my point is that I hope there will never be any. That the discovery should be elsewhere in an ARCH/driver LLD and pmem stays generic. I feel we are not disagreeing, just not communicating. Please explain again, sorry for not understanding. What in the code I sent, you do not like? What in the code is dependent on UEFI organization's paper. That might need to change? Again sorry for being slow. please explain again? Thanks Boaz -- 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