From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GCC3.0 support: Kernel 2.4.5 compilation troubles
Date: Mon, 25 Jun 2001 00:35:54 +0200 [thread overview]
Message-ID: <20010625003554.A1799@werewolf.able.es> (raw)
In-Reply-To: <000f01c0fc3e$b13498c0$d55355c2@microsoft> <E15DxBM-0005zf-00@the-village.bc.nu>
In-Reply-To: <E15DxBM-0005zf-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Jun 24, 2001 at 01:51:16 +0200
On 20010624 Alan Cox wrote:
>
>2. Look back in the kernel archives and you'll find some patches for
> the warnings about multi-line string literals in asm blocks
>
Are there any plans to standarise asm inline code, for example in
Documentation/CodingStyle (of course, in good friendship with gcc-3.0).
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.1 (Cooker) for i586
Linux werewolf 2.4.5-ac17 #2 SMP Fri Jun 22 01:36:07 CEST 2001 i686
prev parent reply other threads:[~2001-06-24 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 23:46 GCC3.0 support: Kernel 2.4.5 compilation troubles Alexander V. Bilichenko
2001-06-23 23:51 ` Alan Cox
2001-06-24 22:35 ` J . A . Magallon [this message]
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=20010625003554.A1799@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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