From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] ARCv2: intc: untangle SMP, MCIP and IDU
Date: Fri, 7 Oct 2016 14:39:10 -0700 [thread overview]
Message-ID: <1fc6dd97-3d03-c2e1-079b-efbfaee63db3@synopsys.com> (raw)
In-Reply-To: <1475861484.2874.44.camel@synopsys.com>
On 10/07/2016 10:31 AM, Alexey Brodkin wrote:
>> They are ugly I agree - but not portable - really ? The whole point is to make
>> > this work on BE w/o changing the src code - this details remains hidden in an
>> > obscure header.
> That's what I learned the hard way.
> At least I was beaten a couple of times yet in both Linux kernel community and
> U-Boot
> one.
Beaten for writing code like above - please point me to those discussions. I'd
love to be educated in art of writing portable code !
prev parent reply other threads:[~2016-10-07 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 20:39 [PATCH] ARCv2: intc: untangle SMP, MCIP and IDU Vineet Gupta
2016-10-06 9:10 ` Alexey Brodkin
2016-10-06 17:10 ` Vineet Gupta
2016-10-07 17:31 ` Alexey Brodkin
2016-10-07 21:39 ` Vineet Gupta [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=1fc6dd97-3d03-c2e1-079b-efbfaee63db3@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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