From: David Daney <ddaney@avtrex.com>
To: Ravi Pratap <Ravi.Pratap@hillcrestlabs.com>
Cc: linux-mips@linux-mips.org
Subject: Re: flush_anon_page for MIPS
Date: Wed, 28 Mar 2007 10:10:56 -0700 [thread overview]
Message-ID: <460AA1A0.1050508@avtrex.com> (raw)
In-Reply-To: <36E4692623C5974BA6661C0B18EE8EDF6CD5B2@MAILSERV.hcrest.com>
Ravi Pratap wrote:
>> From: Atsushi Nemoto [mailto:anemo@mba.ocn.ne.jp]
>> Sent: Monday, March 26, 2007 11:18 PM
>> To: Ravi Pratap
>> Cc: ralf@linux-mips.org; ddaney@avtrex.com;
>> miklos@szeredi.hu; linux-mips@linux-mips.org
>> Subject: Re: flush_anon_page for MIPS
>>
>> On Mon, 26 Mar 2007 19:24:45 -0400, "Ravi Pratap"
>> <Ravi.Pratap@hillcrestlabs.com> wrote:
>>> So I'm trying to backport these changesets and it seems that I need
>>> the changeset that originally introduced kmap_coherent,
>> etc. I tried
>>> some Google searching and found this but I need your help
>> in figuring
>>> out which exact changesets I need.
>>>
>>> Is it this one:
>>>
>>> b895b66990f22a8a030c41390c538660a02bb97f
>>>
>>> ?
>> It was splitted into some parts when merged to mainline.
>>
>> At 2.6.19 cycle:
>> f8829caee311207afbc882794bdc5aa0db5caf33
>> At 2.6.20 cycle:
>> bcd022801ee514e28c32837f0b3ce18c775f1a7b
>> 9de455b20705f36384a711d4a20bcf7ba1ab180b
>> 77fff4ae2b7bba6d66a8287d9ab948e2b6c16145
>>
>> If you only needed kmap_coherent, the first one might be enough.
>
> I just finished backporting your patches to a 2.6.15 kernel and FUSE now
> works just fine.
>
Would you mind posting your patch to this list?
There are some of us that are using the same processor you are that
could find this helpful.
David Daney
next prev parent reply other threads:[~2007-03-28 17:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 22:28 flush_anon_page for MIPS Miklos Szeredi
2007-03-23 14:19 ` Ralf Baechle
2007-03-23 14:19 ` Ralf Baechle
2007-03-23 14:47 ` Franck Bui-Huu
2007-03-23 15:20 ` Ralf Baechle
2007-03-23 21:00 ` Franck Bui-Huu
2007-03-23 21:20 ` Ralf Baechle
2007-03-23 14:51 ` Ravi Pratap
2007-03-23 14:51 ` Ravi Pratap
2007-03-23 15:41 ` Atsushi Nemoto
2007-03-23 15:47 ` Ravi Pratap
2007-03-23 15:47 ` Ravi Pratap
2007-03-23 15:50 ` Atsushi Nemoto
2007-03-26 13:31 ` Atsushi Nemoto
2007-03-26 13:36 ` Ravi Pratap
2007-03-26 13:36 ` Ravi Pratap
2007-03-26 14:33 ` Ralf Baechle
2007-03-23 15:56 ` Ralf Baechle
2007-03-23 15:59 ` Ravi Pratap
2007-03-23 15:59 ` Ravi Pratap
2007-03-23 16:11 ` Maxime Bizon
2007-03-23 16:12 ` Franck Bui-Huu
2007-03-23 16:17 ` Ravi Pratap
2007-03-23 16:17 ` Ravi Pratap
2007-03-23 19:06 ` Ralf Baechle
2007-03-23 22:17 ` Ravi Pratap
2007-03-23 22:17 ` Ravi Pratap
2007-03-23 23:36 ` Ralf Baechle
2007-03-24 0:03 ` David Daney
2007-03-26 13:33 ` Ravi Pratap
2007-03-26 13:33 ` Ravi Pratap
2007-03-26 14:05 ` Ralf Baechle
2007-03-26 22:38 ` Ravi Pratap
2007-03-26 22:38 ` Ravi Pratap
2007-03-26 23:24 ` Ravi Pratap
2007-03-26 23:24 ` Ravi Pratap
2007-03-27 3:17 ` Atsushi Nemoto
2007-03-27 14:51 ` Ravi Pratap
2007-03-27 14:51 ` Ravi Pratap
2007-03-28 14:25 ` Ravi Pratap
2007-03-28 14:25 ` Ravi Pratap
2007-03-28 17:10 ` David Daney [this message]
2007-03-28 18:17 ` Ravi Pratap
2007-03-28 18:17 ` Ravi Pratap
2007-03-28 20:34 ` Ralf Baechle
2007-03-28 20:38 ` David Daney
2007-03-23 15:01 ` Franck Bui-Huu
2007-03-23 15:36 ` Ralf Baechle
2007-03-23 20:52 ` Franck Bui-Huu
2007-03-23 16:22 ` Miklos Szeredi
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=460AA1A0.1050508@avtrex.com \
--to=ddaney@avtrex.com \
--cc=Ravi.Pratap@hillcrestlabs.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.