public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andi Kleen <ak@suse.de>
Cc: "J . A . Magallon" <jamagallon@able.es>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] multiline string cleanup
Date: Mon, 02 Apr 2001 19:50:04 -0400	[thread overview]
Message-ID: <3AC9102C.D053506F@mandrakesoft.com> (raw)
In-Reply-To: <20010330234804.A27780@werewolf.able.es> <oupd7avyng5.fsf@pigdrop.muc.suse.de>

Andi Kleen wrote:
> "J . A . Magallon" <jamagallon@able.es> writes:
> > This is one other try to make kernel sources gcc-3.0 friendly. This cleans
> > some muti-line asm strings in checksum.h and floppy.h (this were the only
> > ones reported in my kernel build, perhaps there are more in drivers I do
> > not use).

> I surely hope the gcc guys will just remove that silly warning again, because
> it makes it impossible to write readable inline assembly now.

If it's a silly warning, then we should turn it off in linux/Makefile. 
I dunno that the kernel can dictate to gcc here what to do...

Also some multiline string cleanups have already made it into the kernel
-- though that is not conclusive, as it may just be maintainer
preference.

	Jeff


-- 
Jeff Garzik       | May you have warm words on a cold evening,
Building 1024     | a full moon on a dark night,
MandrakeSoft      | and a smooth road all the way to your door.

  reply	other threads:[~2001-04-02 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 21:48 [PATCH] multiline string cleanup J . A . Magallon
2001-04-02 21:57 ` Andi Kleen
2001-04-02 23:50   ` Jeff Garzik [this message]
2001-04-02 23:53     ` Andi Kleen

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=3AC9102C.D053506F@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=ak@suse.de \
    --cc=jamagallon@able.es \
    --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