public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Adrian Bunk <bunk@stusta.de>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] kill fatfs_syms.c
Date: Sun, 31 Oct 2004 12:25:34 +0900	[thread overview]
Message-ID: <87k6t74lht.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20041030213343.GZ4374@stusta.de> (Adrian Bunk's message of "Sat, 30 Oct 2004 23:33:43 +0200")

Adrian Bunk <bunk@stusta.de> writes:

> On Sat, Oct 30, 2004 at 07:39:25AM +0100, Christoph Hellwig wrote:
>>...
>> just move this to inode.c
>
> Thanks for this suggestion.
> An updated patch is below.

Thanks. I'll submit after 2.6.10.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

      reply	other threads:[~2004-10-31  3:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30  1:45 [2.6 patch] kill fatfs_syms.c Adrian Bunk
2004-10-30  6:39 ` Christoph Hellwig
2004-10-30 21:33   ` Adrian Bunk
2004-10-31  3:25     ` OGAWA Hirofumi [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=87k6t74lht.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=bunk@stusta.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.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