linux-kernel - Re: [PATCH 0/6] Add a per-dimm structure

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]

Date:	Fri, 16 Mar 2012 09:01:47 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	Borislav Petkov <bp@...64.org>,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/6] Add a per-dimm structure

On Fri, Mar 16, 2012 at 12:44:01PM -0300, Mauro Carvalho Chehab wrote:
> Em 16-03-2012 12:30, Greg KH escreveu:
> > On Fri, Mar 16, 2012 at 05:47:52AM -0300, Mauro Carvalho Chehab wrote:
> >> 2) per Greg's request, we should not use struct sysdev, using instead,
> >>    struct device. That means that everything under
> >> 	/sys/devices/system/edac/mc/
> >>    will move to another place, likely:
> >> 	/sys/devices/ras/
> > 
> > No, you can keep things under /sys/devices/system/edac/ if you use a
> > struct device, no need to move things and break userspace tools if you
> > don't have to.
> 
> Hmm... How?

Just point your parent of your device to the same place.  Converting
from using 'struct sysdev' is easy, as the conversion is already done
in-tree to real 'struct device' so there shouldn't be any problems.

Or am I missing something here?

thanks,

greg k-h
--
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/