From: Pavel Fedin <p.fedin@samsung.com>
To: 'Masahiro Yamada' <yamada.masahiro@socionext.com>,
'Michal Marek' <mmarek@suse.com>
Cc: 'Linux Kbuild mailing list' <linux-kbuild@vger.kernel.org>
Subject: RE: [PATCH TRIVIAL v2] Avoid conflict with host definitions when cross-compiling
Date: Tue, 25 Aug 2015 10:47:03 +0300 [thread overview]
Message-ID: <00dc01d0df0a$3bda3e90$b38ebbb0$@samsung.com> (raw)
In-Reply-To: <CAK7LNARtmsBOticVU1dgx1iAXq8m5Q-pi-GkGe6E08HcqeHZZw@mail.gmail.com>
Hello!
> I am not happy with getting weird code to work around issues on
> non-Linux systems.
What is your criteria of being weird? Why are four #undef's weird ?
Do you want to tell that "all OSes except Linux are weird?" Isn't it too childish?
I can say that i use Windows as my desktop OS because only Windows has all the necessary corporate software, and using Linux inside a virtual machine just for running builds is inconvenient. And vast majority of corporate users use Windows.
Well, it's just my opinion, i'm not going to start another "Lin vs Win" war, i think it's just stupid.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-08-25 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 10:52 [PATCH TRIVIAL v2] Avoid conflict with host definitions when cross-compiling Pavel Fedin
2015-08-20 11:31 ` Michal Marek
2015-08-20 12:31 ` Pavel Fedin
2015-08-20 12:38 ` Michal Marek
2015-08-20 13:18 ` Pavel Fedin
2015-08-21 12:49 ` Michal Marek
2015-08-24 6:44 ` Pavel Fedin
2015-08-24 16:36 ` Masahiro Yamada
2015-08-25 7:47 ` Pavel Fedin [this message]
2015-08-25 8:18 ` Masahiro Yamada
2015-08-25 9:27 ` Pavel Fedin
2015-08-25 9:56 ` Michal Marek
2015-08-25 9:59 ` Pavel Fedin
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='00dc01d0df0a$3bda3e90$b38ebbb0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.