linux-kernel - Re: [PATCH 0/3] Fix some outdated pre-kernfs doc references

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] [day] [month] [year] [list]

Date:	Sat, 12 Sep 2015 14:15:12 -0600
From:	Jonathan Corbet <corbet@....net>
To:	ulfalizer.lkml@...il.com
Cc:	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	harryxiyou@...il.com, jlbec@...lplan.org, ulfalizer@...il.com,
	gregkh@...uxfoundation.org, shane.seymour@...com, tj@...nel.org,
	bvanassche@....org, serue@...ibm.com
Subject: Re: [PATCH 0/3] Fix some outdated pre-kernfs doc references

On Wed,  2 Sep 2015 14:34:51 +0200
ulfalizer.lkml@...il.com wrote:

> sysfs-tagging.txt contains more outdated references (e.g., to various
> kobj_ns_*() functions that no longer exist), but hopefully it should be in
> a better shape than before. I'm new to sysfs internals in general.
> 
> The configfs change is a guess that seemed reasonable.
> 
> Ulf Magnusson (3):
>   sysfs.txt: fix pre-kernfs sysfs_dirent reference
>   sysfs-tagging.txt: fix pre-kernfs references

So, I sure would have rather seen a patch that actually documents kernfs
rather than just swapping a few names here and there, but so be it.  I've
applied these two to the docs tree, since they make things better than
they were before.

>   configfs: fix pre-kernfs sysfs_dirent reference

Not sure who handles configfs patches these days, but it's not me, so
I've not done anything with this one.

Thanks,

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