From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] ARM: remove references to non-existent fastfpe
Date: Wed, 14 Oct 2009 20:03:33 +0100 [thread overview]
Message-ID: <20091014190333.GA28948@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <200910142021.59118.peter@peter-teichmann.de>
On Wed, Oct 14, 2009 at 08:21:58PM +0200, Peter Teichmann wrote:
> I agree to Alan. It seems reasonable at least to include a stub as he
> suggests. However, since FastFPE was not updated for some years now, maybe
> the burden of maintaining patches is not so heavy in anymore? Maybe we can
> as well just include the latest version now? It becomes more and more
> difficult to find the source for someone who is interested in it.
The easiest and least risky approach would be to leave it as is - we
know it's not causing any problems with it there, and it's not causing
any run-time bloat.
next prev parent reply other threads:[~2009-10-14 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 14:02 [PATCH 1/6] ARM: remove unused declaration of fpundefinstr Alan Jenkins
2009-10-09 14:02 ` [PATCH 2/6] ARM: remove out of date comment Alan Jenkins
2009-10-09 14:02 ` [PATCH 3/6] ARM: update Kconfig help text for floating point Alan Jenkins
2009-10-09 14:02 ` [PATCH 4/6] ARM: remove references to non-existent fastfpe Alan Jenkins
2009-10-09 16:55 ` Russell King - ARM Linux
2009-10-10 8:41 ` Alan Jenkins
2009-10-14 18:21 ` Peter Teichmann
2009-10-14 19:03 ` Russell King - ARM Linux [this message]
2009-10-14 20:33 ` Alan Jenkins
2009-10-09 14:02 ` [PATCH 5/6] ARM: nwfpe can no longer be built as a module - remove dead code (part 1 of 2) Alan Jenkins
2009-10-09 14:02 ` [PATCH 6/6] ARM: newfpe can no longer be compiled as a module - cleanup (part 2 " Alan Jenkins
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=20091014190333.GA28948@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).