All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
	Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	"Martin J. Bligh" <mjbligh@us.ibm.com>,
	Christian Borntraeger <CBORNTRA@de.ibm.com>
Subject: Re: [RFC/T 0/6] sysfs backing store (with symlink)
Date: Thu, 5 Feb 2004 13:59:24 -0600	[thread overview]
Message-ID: <20040205195923.GI31138@waste.org> (raw)
In-Reply-To: <20040204113758.GA4234@in.ibm.com>

On Wed, Feb 04, 2004 at 05:07:58PM +0530, Maneesh Soni wrote:
> Hi All,
> 
> Please find following patches for sysfs-backing store. This version has
> support for putting symlinks also on backing store. Earlier it has support
> for text/binary attribute files. 
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107269078726254&w=2
> 
> Apart from a few bug fixes, the main change in this version is for symlinks. 
> sysfs_create_link() now does not create dentry/inode for the link, but 
> allocates a sysfs_dirent and adds it the parent sysfs_dirent's s_children 
> list. dentry/inode for the link is created when the symlink is first looked up. 
> 
> I request Martin and Mackall to _replace_ the old patch set with the 
> new one in their trees.

I finally got around to testing this in tiny, and it works quite well.
I actually got it working in my mem=2m test case, though it was a
little tight.

It's the philosophy of -tiny to make all new features optional, so I'm
currently in the process of making it a config option and am going
back through and adding CONFIG_SYSFS_BACK. Will post a new version
as part of my next -tiny shortly.

-- 
Matt Mackall : http://www.selenic.com : Linux development and consulting

      parent reply	other threads:[~2004-02-05 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 11:37 [RFC/T 0/6] sysfs backing store (with symlink) Maneesh Soni
2004-02-04 11:38 ` [RFC/T 1/6] " Maneesh Soni
2004-02-04 11:39   ` [RFC/T 2/6] " Maneesh Soni
2004-02-04 11:40     ` [RFC/T 3/6] " Maneesh Soni
2004-02-04 11:40       ` [RFC/T 4/6] " Maneesh Soni
2004-02-04 11:41         ` [RFC/T 5/6] " Maneesh Soni
2004-02-04 11:41           ` [RFC/T 6/6] " Maneesh Soni
2004-02-05 19:59 ` Matt Mackall [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=20040205195923.GI31138@waste.org \
    --to=mpm@selenic.com \
    --cc=CBORNTRA@de.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=mjbligh@us.ibm.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.