From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nicklas Widlund Bjurman <lordmetroid@gmail.com>
Cc: linux-kernel@vger.kernel.org,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: SYS_rename for FAT32
Date: Mon, 26 Jan 2009 16:38:04 -0800 [thread overview]
Message-ID: <497E576C.7050605@oracle.com> (raw)
In-Reply-To: <36d886900901261633r3b3018b4led0bd980816f4d88@mail.gmail.com>
Nicklas Widlund Bjurman wrote:
> Hi, I'm a new Linux kernel developer.
>
> I filed a bug two weeks ago( https://bugs.launchpad.net/bugs/315782 )
> and now after some further research to determine the bug's location, I
> am now determined to patch it.
>
> I searched http://lxr.linux.no/linux+v2.6.28.2/+search after
> SYS_rename to see what the process is for renaming a file however I
> can't find anything. Could anyone knowledgeable of the kernel point me
> to where I should start digging?
Hi,
I suggest that you cc: the FAT fs maintainer. (done)
--
~Randy
prev parent reply other threads:[~2009-01-27 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 0:33 SYS_rename for FAT32 Nicklas Widlund Bjurman
2009-01-27 0:38 ` Randy Dunlap [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=497E576C.7050605@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=lordmetroid@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