public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Thery <benjamin.thery@bull.net>
To: Greg KH <gregkh@suse.de>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] sysfs tagged directories V5
Date: Fri, 13 Jun 2008 14:17:17 +0200	[thread overview]
Message-ID: <4852654D.9060306@bull.net> (raw)
In-Reply-To: <20080610230058.GA25072@suse.de>

Greg KH wrote:
> On Tue, Jun 10, 2008 at 05:50:24PM -0500, Serge E. Hallyn wrote:
>> Quoting Benjamin Thery (benjamin.thery@bull.net):
>>> Greg,
>>>
>>> Here is an updated version of the sysfs tagged directories that improves
>>> a bit the situation over the previous one. 
>>>
[...]
>>>
>>> The generic part can be merge with patch 05 ("sysfs: Implement sysfs 
>>> tagged directory support.") but I left it separate for now to ease 
>>> reviews.
>> Thanks.  Not nearly as radical as I'd feared.
>>
>> Greg, does this address your concern?  It stops the need to put any
>> non-braindead code (i.e. the _exit notifier stuff) in fs/sysfs/mount.c for
>> any new namespaces needing sysfs tagging, leaving only simple
>> comparison/assignments.
> 
> Sorry, I've been swamped with other things this week and haven't gotten
> a chance to look this over.  Hopefully by the end of the week...  It's
> in my queue though, don't worry it will not get lost.

Greg,

I've ported the patchset to 2.6.26-rc5-mm3 yesterday and I have just
finished testing it. Will this help you if I send you an up-to-date
tarball with this new version? or is it fine for you to review the 
patchset I sent last week (based on 2.6.26-rc2-mm1)?

Tell me what you prefer.

Benjamin

> 
> thanks,
> 
> greg k-h
> 
> 


-- 
B e n j a m i n   T h e r y  - BULL/DT/Open Software R&D

    http://www.bull.com

      reply	other threads:[~2008-06-13 12:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 15:46 [PATCH 00/11] sysfs tagged directories V5 Benjamin Thery
2008-06-06 15:47 ` [PATCH 01/11] sysfs: Support for preventing unmounts Benjamin Thery
2008-06-06 15:47 ` [PATCH 02/11] sysfs: sysfs_get_dentry add a sb parameter Benjamin Thery
2008-06-06 15:47 ` [PATCH 03/11] sysfs: Implement __sysfs_get_dentry Benjamin Thery
2008-06-06 15:47 ` [PATCH 04/11] sysfs: Rename Support multiple superblocks Benjamin Thery
2008-06-06 15:47 ` [PATCH 05/11] sysfs: sysfs_chmod_file handle " Benjamin Thery
2008-06-06 15:47 ` [PATCH 06/11] sysfs: Implement sysfs tagged directory support Benjamin Thery
2008-06-06 15:48 ` [PATCH 07/11] sysfs: Implement sysfs_delete_link and sysfs_rename_link Benjamin Thery
2008-06-06 15:48 ` [PATCH 08/11] driver core: Implement tagged directory support for device classes Benjamin Thery
2008-06-06 15:48 ` [PATCH 09/11] sysfs: add sysfs_ns_exit routine Benjamin Thery
2008-06-06 15:48 ` [PATCH 10/11] netns: Enable tagging for net_class directories in sysfs Benjamin Thery
2008-06-06 15:48 ` [PATCH 11/11] sysfs: user namespaces: fix bug with clone(CLONE_NEWUSER) with fairsched Benjamin Thery
2008-06-10 22:41   ` Serge E. Hallyn
2008-06-10 22:50 ` [PATCH 00/11] sysfs tagged directories V5 Serge E. Hallyn
2008-06-10 23:00   ` Greg KH
2008-06-13 12:17     ` Benjamin Thery [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=4852654D.9060306@bull.net \
    --to=benjamin.thery@bull.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.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