mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: ulfalizer.lkml@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	harryxiyou@gmail.com, jlbec@evilplan.org, ulfalizer@gmail.com,
	gregkh@linuxfoundation.org, shane.seymour@hp.com, tj@kernel.org,
	bvanassche@acm.org, serue@us.ibm.com
Subject: Re: [PATCH 0/3] Fix some outdated pre-kernfs doc references
Date: Sat, 12 Sep 2015 14:15:12 -0600	[thread overview]
Message-ID: <20150912141512.4ebf3668@lwn.net> (raw)
In-Reply-To: <1441197294-11723-1-git-send-email-ulfalizer.lkml@gmail.com>

On Wed,  2 Sep 2015 14:34:51 +0200
ulfalizer.lkml@gmail.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

      parent reply	other threads:[~2015-09-12 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 12:34 ulfalizer.lkml
2015-09-02 12:34 ` [PATCH 1/3] sysfs.txt: fix pre-kernfs sysfs_dirent reference ulfalizer.lkml
2015-09-02 12:34   ` [PATCH 2/3] sysfs-tagging.txt: fix pre-kernfs references ulfalizer.lkml
2015-09-02 12:34     ` [PATCH 3/3] configfs: fix pre-kernfs sysfs_dirent reference ulfalizer.lkml
2015-09-12 20:15 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150912141512.4ebf3668@lwn.net \
    --to=corbet@lwn.net \
    --cc=bvanassche@acm.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harryxiyou@gmail.com \
    --cc=jlbec@evilplan.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=shane.seymour@hp.com \
    --cc=tj@kernel.org \
    --cc=ulfalizer.lkml@gmail.com \
    --cc=ulfalizer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®