From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v2] arch: use ASM_NL instead of ';' for assembler new line character in the macro
Date: Thu, 9 Jan 2014 12:11:26 +0530 [thread overview]
Message-ID: <52CE4496.5030401@synopsys.com> (raw)
In-Reply-To: <52CA76D3.2010102@suse.cz>
Forwarding to Chen's email address:
On Monday 06 January 2014 02:56 PM, Michal Marek wrote:
> On 2014-01-06 06:36, Vineet Gupta wrote:
>> Hi Michal,
>>
>> On Friday 03 January 2014 06:08 PM, Michal Marek wrote:
>>> On 2013-11-21 10:58, Vineet Gupta wrote:
>>>> On 11/01/2013 11:15 AM, Vineet Gupta wrote:
>>>>> +CC Sam, Tim, Joe, Michal, David
>>>>>
>>>>> Guys can you please take a look at this patch and suggest the best way to merge.
>>>>>
>>>>> The root cause is some gas ports (including ARC) use ';' for comment (vs. newline)
>>>>> More background at https://lkml.org/lkml/2013/10/24/365
>>>> Ping ! Any objections to this. Given that this is exception case, it is simpler
>>>> than defining a Kconfig control.
>>>>
>>>> -Vineet
>>>>>
>>>>> On 10/29/2013 07:21 AM, Chen Gang wrote:
>>>>>> For some assemblers, they use another character as newline in a macro
>>>>>> (e.g. arc uses '`'), so for generic assembly code, need use ASM_NL (a
>>>>>> macro) instead of ';' for it.
>>>>>>
>>>>>> Also need notice about code styles ('\t' for each line).
>>>>>>
>>>>>>
>>>>>> Signed-off-by: Chen Gang <gang.chen@asianux.com>
>
>>
>> Did you hit reply by mistake - as I can't seem to find any comments...
>
> Oops :). I wanted to ask if this is the final patch that should be
> merged, or if there are more known instances of .S code that needs
> s/;/ASM_NL/. I did not find any suspects outside arch/ by grepping. If
> this is the final patch, Chen, could you please resubmit it? I do not
> have the original copy.
>
> Michal
>
-Vineet
next prev parent reply other threads:[~2014-01-09 6:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 10:30 [PATCH] arch: use ASM_NL instead of ';' for assembler new line character in the macro Chen Gang
2013-10-28 11:18 ` Max Filippov
2013-10-29 7:57 ` Chen Gang
2013-10-29 7:57 ` Chen Gang
2013-10-29 8:34 ` Max Filippov
2013-10-29 8:34 ` Max Filippov
2013-10-29 8:47 ` Chen Gang
2013-10-28 13:45 ` Vineet Gupta
2013-10-29 1:04 ` Chen Gang
2013-10-29 1:39 ` Chen Gang
2013-10-29 1:51 ` [PATCH v2] " Chen Gang
2013-10-29 5:55 ` Vineet Gupta
2013-10-29 6:07 ` Chen Gang
2013-11-01 5:45 ` Vineet Gupta
2013-11-21 9:58 ` Vineet Gupta
2013-11-21 10:52 ` Chen Gang
2014-01-03 12:38 ` Michal Marek
2014-01-03 12:38 ` Michal Marek
2014-01-06 5:36 ` Vineet Gupta
2014-01-06 9:26 ` Michal Marek
2014-01-09 6:41 ` Vineet Gupta [this message]
2014-01-10 15:48 ` Chen Gang
2014-01-10 15:48 ` Chen Gang
2014-01-12 1:59 ` [PATCH v3] " Chen Gang
2014-01-18 9:44 ` Chen Gang
2014-01-21 4:55 ` Vineet Gupta
2014-01-25 11:07 ` Chen Gang
2014-01-27 21:57 ` Michal Marek
2014-01-30 5:41 ` Chen Gang
2014-01-30 5:41 ` Chen Gang
2013-10-29 10:39 ` [PATCH] " David Howells
2013-10-29 11:53 ` Chen Gang
2013-10-29 13:59 ` David Howells
2013-10-30 0:57 ` Chen Gang
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=52CE4496.5030401@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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 NNTP newsgroup(s).