All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: linux-kbuild@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH TRIVIAL v2] Avoid conflict with host definitions when cross-compiling
Date: Thu, 20 Aug 2015 14:38:09 +0200	[thread overview]
Message-ID: <55D5CA31.8090401@suse.com> (raw)
In-Reply-To: <018a01d0db44$35ed5630$a1c80290$@samsung.com>

On 2015-08-20 14:31, Pavel Fedin wrote:
>  Hello!
> 
>> Thanks, applied to kbuild.git#kbuild. But it seems that
>> arch/x86/tools/relocs needs the same fix.
> 
>  Perhaps. I tried to compile only ARM kernels, no x86.
> 
>  By the way, i have several more fixes which could increase kbuild portability. For example, there
> are several issues on Cygwin with .exe extensions of some tools. Could we upstream them also?

If you already have the patches, it won't hurt to send them. Although I
was under the impression that the .exe suffix is somehow automagically
handled by Cygwin..?

Michal


  reply	other threads:[~2015-08-20 12:38 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 [this message]
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
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=55D5CA31.8090401@suse.com \
    --to=mmarek@suse.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=p.fedin@samsung.com \
    --cc=trivial@kernel.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 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.