From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: Experimental fix for my memcpy_{to,from}fs problem
Date: Thu, 3 Jun 2004 14:37:12 +0000 [thread overview]
Message-ID: <20040603143711.GA13536@lichen.truemesh.com> (raw)
In-Reply-To: <20040603141438.GG26330@duckman.distro.conectiva>
On Thu, Jun 03, 2004 at 11:14:39AM -0300, Eduardo Pereira Habkost wrote:
> Hi, Mike,
>
> On Thu, Jun 03, 2004 at 08:02:18AM -0600, Miguel Bolanos wrote:
> > Applied, but i did some changes on the patch, please read bellow.
> The changes are on CVS? I did an 'cvs update', and the last revision of
> user.c (1.17) doesn't contain any of these changes.
Does sf still lag public anoncvs one day behind?
Paul
next prev parent reply other threads:[~2004-06-03 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 21:32 memcpy_fromfs() failing. Wrong variable offsets Eduardo Pereira Habkost
2004-06-01 22:02 ` Experimental fix for my memcpy_{to,from}fs problem Eduardo Pereira Habkost
2004-06-01 22:30 ` Eduardo Pereira Habkost
2004-06-02 2:57 ` Miguel Bolanos
2004-06-02 16:25 ` Eduardo Pereira Habkost
2004-06-03 14:02 ` Miguel Bolanos
2004-06-03 14:14 ` Eduardo Pereira Habkost
2004-06-03 14:37 ` Paul Nasrat [this message]
2004-06-02 1:33 ` claudio
2004-06-02 20:53 ` Miguel Bolanos
2004-06-02 3:05 ` Miguel Bolanos
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=20040603143711.GA13536@lichen.truemesh.com \
--to=pauln@truemesh.com \
--cc=linux-8086@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