From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Florian Lohoff" <flo@rfc822.org>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)
Date: Thu, 13 Dec 2001 12:13:00 -0500 [thread overview]
Message-ID: <070501c183f9$6b02de50$5601010a@prefect> (raw)
In-Reply-To: 20011213170410.GB25296@paradigm.rfc822.org
----- Original Message -----
From: "Florian Lohoff" <flo@rfc822.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Thursday, December 13, 2001 12:04 PM
Subject: Re: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)
> There is - But autoconf in the current version is broken and needs
> this to gather the endianess - As we currently have to live with it
> this is a 2.4 issue - 2.5 should fix this and remove endianess from
> /proc/cpuinfo.
I understand, thanks for the explanation. So the patch should only go in
the 2.4 branch?
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)
Date: Thu, 13 Dec 2001 12:13:00 -0500 [thread overview]
Message-ID: <070501c183f9$6b02de50$5601010a@prefect> (raw)
Message-ID: <20011213171300.nnTZwhwlBMLu_EErmXkWqkxxZ6w-Zmls8WXaL0SwEmE@z> (raw)
In-Reply-To: 20011213170410.GB25296@paradigm.rfc822.org
----- Original Message -----
From: "Florian Lohoff" <flo@rfc822.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Thursday, December 13, 2001 12:04 PM
Subject: Re: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)
> There is - But autoconf in the current version is broken and needs
> this to gather the endianess - As we currently have to live with it
> this is a 2.4 issue - 2.5 should fix this and remove endianess from
> /proc/cpuinfo.
I understand, thanks for the explanation. So the patch should only go in
the 2.4 branch?
Regards,
Brad
next prev parent reply other threads:[~2001-12-13 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 16:39 [PATCH] /proc/cpuinfo endianess (autoconf dependencie) Florian Lohoff
2001-12-13 16:56 ` Florian Lohoff
2001-12-13 17:01 ` Bradley D. LaRonde
2001-12-13 17:01 ` Bradley D. LaRonde
2001-12-13 17:04 ` Florian Lohoff
2001-12-13 17:13 ` Bradley D. LaRonde [this message]
2001-12-13 17:13 ` Bradley D. LaRonde
2001-12-13 17:05 ` Florian Lohoff
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='070501c183f9$6b02de50$5601010a@prefect' \
--to=brad@ltc.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
/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