LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@muc.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] No need to use -traditional for processing asm in i386/kernel/
Date: Thu, 15 Feb 2007 23:44:39 +0100	[thread overview]
Message-ID: <20070215224439.GA7909@uranus.ravnborg.org> (raw)
In-Reply-To: <45D4CE50.9020604@goop.org>

On Thu, Feb 15, 2007 at 01:19:12PM -0800, Jeremy Fitzhardinge wrote:
> No need to use -traditional for processing asm in i386/kernel/
> 
> Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com>

Any possibility that you could 'fix' the three remaining
uses of -traditional in i386?

	Sam

  reply	other threads:[~2007-02-15 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 21:19 Jeremy Fitzhardinge
2007-02-15 22:44 ` Sam Ravnborg [this message]
2007-02-15 23:48   ` Jeremy Fitzhardinge

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=20070215224439.GA7909@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ak@muc.de \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] No need to use -traditional for processing asm in i386/kernel/' \
    /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

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).