public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Andrew Pinski <pinskia@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Uros Bizjak <ubizjak@gmail.com>, Hongtao Liu <crazylht@gmail.com>
Subject: Re: [PATCH][i386] target: support spaces in target attribute.
Date: Mon, 18 Oct 2021 13:23:54 +0200	[thread overview]
Message-ID: <bde5cd38-024a-bd00-c16f-c7619c2c141a@suse.cz> (raw)
In-Reply-To: <b3157c54-9ece-7216-dc35-fc50c65f75a7@suse.cz>

On 10/11/21 13:17, Martin Liška wrote:
> On 10/4/21 23:02, Andrew Pinski wrote:
>> It might be useful to skip tabs for the same reason as spaces really.
> 
> Sure, be my guest.
> 
> Martin

May I please ping this i386-specific patch?

Thanks,
Martin

  reply	other threads:[~2021-10-18 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 15:11 Martin Liška
2021-10-04 21:02 ` Andrew Pinski
2021-10-11 11:17   ` Martin Liška
2021-10-18 11:23     ` Martin Liška [this message]
2021-10-18 15:12       ` Uros Bizjak
2021-10-19  6:49         ` Martin Liška

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=bde5cd38-024a-bd00-c16f-c7619c2c141a@suse.cz \
    --to=mliska@suse.cz \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pinskia@gmail.com \
    --cc=ubizjak@gmail.com \
    /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).