public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, neilb@suse.de,
	linus.walleij@linaro.org, ashutosh.dixit@intel.com,
	kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH 1/6] kernfs: s/sysfs_dirent/kernfs_node/ and rename its friends accordingly
Date: Wed, 11 Dec 2013 13:22:38 -0800	[thread overview]
Message-ID: <20131211212238.GC20491@kroah.com> (raw)
In-Reply-To: <1386789118-24733-2-git-send-email-tj@kernel.org>

On Wed, Dec 11, 2013 at 02:11:53PM -0500, Tejun Heo wrote:
> kernfs has just been separated out from sysfs and we're already in
> full conflict mode.  Nothing can make the situation any worse.  Let's
> take the chance to name things properly.
> 
> This patch performs the following renames.
> 
> * s/sysfs_elem_dir/kernfs_elem_dir/
> * s/sysfs_elem_symlink/kernfs_elem_symlink/
> * s/sysfs_elem_attr/kernfs_elem_file/
> * s/sysfs_dirent/kernfs_node/
> * s/sd/kn/ in kernfs proper
> * s/parent_sd/parent/
> * s/target_sd/target/
> * s/dir_sd/parent/
> * s/to_sysfs_dirent()/rb_to_kn()/
> * misc renames of local vars when they conflict with the above
> 
> Because md, mic and gpio dig into sysfs details, this patch ends up
> modifying them.  All are sysfs_dirent renames and trivial.  While we
> can avoid these by introducing a dummy wrapping struct sysfs_dirent
> around kernfs_node, given the limited usage outside kernfs and sysfs
> proper, I don't think such workaround is called for.

Ugh, why are those drivers digging into sysfs core bits anyway?  I'll
look and see if they should be fixed up as well, as I really doubt a
"normal" driver should ever care about this type of thing...

thanks,

greg k-h

  reply	other threads:[~2013-12-11 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 19:11 [PATCHSET driver-core-next] kernfs: s/sysfs/kernfs/ Tejun Heo
2013-12-11 19:11 ` [PATCH 1/6] kernfs: s/sysfs_dirent/kernfs_node/ and rename its friends accordingly Tejun Heo
2013-12-11 21:22   ` Greg KH [this message]
2013-12-11 21:27     ` Greg KH
2013-12-12  9:52   ` Linus Walleij
2013-12-11 19:11 ` [PATCH 2/6] kernfs: drop s_ prefix from kernfs_node members Tejun Heo
2013-12-11 19:11 ` [PATCH 3/6] kernfs: s/sysfs/kernfs/ in various data structures Tejun Heo
2013-12-11 19:11 ` [PATCH 4/6] kernfs: s/sysfs/kernfs/ in constants Tejun Heo
2013-12-11 19:11 ` [PATCH 5/6] kernfs: s/sysfs/kernfs/ in global variables Tejun Heo
2013-12-11 19:11 ` [PATCH 6/6] kernfs: s/sysfs/kernfs/ in internal functions and whatever is left Tejun Heo

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=20131211212238.GC20491@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ashutosh.dixit@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tj@kernel.org \
    /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