From: R.E.Wolff@bitwizard.nl (Rogier Wolff)
To: Russell King <rmk@arm.linux.org.uk>
Cc: Rogier Wolff <R.E.Wolff@bitwizard.nl>,
Tigran Aivazian <tigran@veritas.com>,
Patrick van de Lageweg <patrick@bitwizard.nl>,
Rogier Wolff <wolff@bitwizard.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New user space serial port driver
Date: Fri, 1 Dec 2000 00:09:25 +0100 (MET) [thread overview]
Message-ID: <200011302309.AAA04497@cave.bitwizard.nl> (raw)
In-Reply-To: <200011301654.QAA01657@raistlin.arm.linux.org.uk> from Russell King at "Nov 30, 2000 04:54:26 pm"
Russell King wrote:
> Rogier Wolff writes:
> > Documentation bug. Not code bug.
>
> In which case, can we put it in as a documentation fix rather than changing
> the compiler output? ie, /* = { NULL, } */ ?
Because I care more about the 4 bytes of extra source than the
4 bytes of extra object.
I consider the 4 bytes of extra object code a compiler bug, and if we
start catering for that, the bug in the compiler will never be fixed.
This is similar to how Linus forced the recognition of the
"unroll-loops" bug by the gcc team.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 8:04 [PATCH] New user space serial port driver Patrick van de Lageweg
2000-11-30 8:22 ` Tigran Aivazian
2000-11-30 9:47 ` Rogier Wolff
2000-11-30 15:00 ` Russell King
2000-11-30 16:47 ` Rogier Wolff
2000-11-30 16:54 ` Russell King
2000-11-30 23:09 ` Rogier Wolff [this message]
2000-12-02 21:59 ` Pavel Machek
2000-12-07 12:38 ` Jamie Lokier
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=200011302309.AAA04497@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@bitwizard.nl \
--cc=rmk@arm.linux.org.uk \
--cc=tigran@veritas.com \
--cc=wolff@bitwizard.nl \
/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.