From: "P. Christeas" <p_christ@hol.gr>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: Fixes for uaccess.h with gcc >= 4.0.1
Date: Mon, 23 Jan 2006 17:18:38 +0200 [thread overview]
Message-ID: <200601231718.40581.p_christ@hol.gr> (raw)
In-Reply-To: <20060123150507.GA18665@linux-mips.org>
On Monday 23 January 2006 5:05 pm, Ralf Baechle wrote:
> I'd appreciate if somebody with gcc 4.0.1 could test this kernel patch
> below.
>
> Ralf
Is that for 2.4?
2.6 doesn't seem to have that problem..
WARNING: multiple messages have this Message-ID (diff)
From: "P. Christeas" <p_christ@hol.gr>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: Fixes for uaccess.h with gcc >= 4.0.1
Date: Mon, 23 Jan 2006 17:18:38 +0200 [thread overview]
Message-ID: <200601231718.40581.p_christ@hol.gr> (raw)
Message-ID: <20060123151838.pvVt26kyfo6-UM3fi4fpBhRVZN-dxtLW-YnlDBZ7pfs@z> (raw)
In-Reply-To: <20060123150507.GA18665@linux-mips.org>
On Monday 23 January 2006 5:05 pm, Ralf Baechle wrote:
> I'd appreciate if somebody with gcc 4.0.1 could test this kernel patch
> below.
>
> Ralf
Is that for 2.4?
2.6 doesn't seem to have that problem..
next prev parent reply other threads:[~2006-01-23 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 15:05 Fixes for uaccess.h with gcc >= 4.0.1 Ralf Baechle
2006-01-23 15:18 ` P. Christeas [this message]
2006-01-23 15:18 ` P. Christeas
2006-01-23 15:37 ` Ralf Baechle
2006-01-23 15:50 ` P. Christeas
2006-01-23 16:13 ` Thiemo Seufer
2006-01-23 15:45 ` Martin Michlmayr
2006-01-23 16:04 ` Rojhalat Ibrahim
2006-01-23 16:16 ` Ralf Baechle
2006-01-24 0:01 ` Stuart Anderson
2006-01-23 16:13 ` Martin Michlmayr
2006-02-07 20:21 ` Richard Sandiford
2006-02-10 1:34 ` Ralf Baechle
2006-02-11 13:44 ` Atsushi Nemoto
2006-02-14 6:57 ` Atsushi Nemoto
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=200601231718.40581.p_christ@hol.gr \
--to=p_christ@hol.gr \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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.