From: Andrew Morton <akpm@linux-foundation.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Adds ratelimit_state_init()
Date: Wed, 19 May 2010 13:57:54 -0700 [thread overview]
Message-ID: <20100519135754.17afd645.akpm@linux-foundation.org> (raw)
In-Reply-To: <87k4r3cqgz.fsf@devron.myhome.or.jp>
On Mon, 17 May 2010 09:38:20 +0900
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
> Andrew, this is the part of fatfs error ratelimit. I.e. fatfs change is
> depending to this patch.
>
> I guess this area usually is sent to you. But, if this patch
> wasn't applied before fatfs change, fatfs will break.
>
> Well, so, can I pass fatfs patch to you? Or, I should apply this to
> fatfs-tree too?
Is OK, I'll send them both in for 2.6.35, thanks.
prev parent reply other threads:[~2010-05-19 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 0:38 [PATCH 1/2] Adds ratelimit_state_init() OGAWA Hirofumi
2010-05-17 0:39 ` [PATCH 2/2] fat: ratelimit corruption report OGAWA Hirofumi
2010-05-19 20:57 ` Andrew Morton [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=20100519135754.17afd645.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--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;
as well as URLs for NNTP newsgroup(s).