public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: v9fs-developer@lists.sourceforge.net, akpm@osdl.org,
	linux-fsdevel@vger.kernel.org
Subject: [CORRECTION] [-mm PATCH] v9fs: Clean-up vfs_inode and setattr functions
Date: Wed, 22 Jun 2005 08:26:40 -0500	[thread overview]
Message-ID: <a4e6962a05062206262190276b@mail.gmail.com> (raw)
In-Reply-To: <200506220125.j5M1P1Rh022077@ms-smtp-05-eri0.texas.rr.com>

On 6/21/05, ericvh@gmail.com <ericvh@gmail.com> wrote:
> Cleanup code in v9fs vfs_inode as suggested by Alexy Dobriyan.

Make that Alexey Dobriyan.

> Did some major revamping of the v9fs setattr code to remove unnecessary
> allocations and clean up some dead-code.
> 
> Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
> 

[patch contents remain the same]

            -eric

      reply	other threads:[~2005-06-22 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22  1:23 [-mm PATCH] v9fs: Clean-up vfs_inode and setattr functions ericvh
2005-06-22 13:26 ` Eric Van Hensbergen [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=a4e6962a05062206262190276b@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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