public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gcc-patches@gcc.gnu.org,  law@redhat.com
Subject: Re: PATCH: Add .type pseudo-op to 68K soft-float routines
Date: Mon, 30 Jul 2007 20:06:00 -0000	[thread overview]
Message-ID: <46AE3DD5.7010608@codesourcery.com> (raw)
In-Reply-To: <jefy361c9f.fsf@sykes.suse.de>

Andreas Schwab wrote:
> Mark Mitchell <mark@codesourcery.com> writes:
> 
>> If there are no objections from the 68K maintainers, I will commit
>> this in 48 hours.
> 
> No objections, just a small nit:
> 
>> +/* The .proc pseudo-op is accepted, but ignored, by GAS.  We could just		  define this to the empty string for non-ELF systems, but defining it
> 
> A newline was lost here.

Good catch!  I checked it in, with that change.

Please let me know if there are any problems.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

      reply	other threads:[~2007-07-30 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 21:06 Mark Mitchell
2007-07-30 10:32 ` Andreas Schwab
2007-07-30 20:06   ` Mark Mitchell [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=46AE3DD5.7010608@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=schwab@suse.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).