All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nadav Amit <namit@vmware.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Michal Marek <michal.lkml@markovi.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	X86 ML <x86@kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Makefile: Fix distcc compilation with x86 macros
Date: Thu, 29 Nov 2018 00:38:07 +0000	[thread overview]
Message-ID: <5682CCB4-B7D3-4DDC-81BB-2D4DCE968A3D@vmware.com> (raw)
In-Reply-To: <be24a6eb-ebf0-8d9f-0051-681f0da66109@deltatee.com>

> On Nov 28, 2018, at 3:09 PM, Logan Gunthorpe <logang@deltatee.com> wrote:
> 
> 
> 
> On 2018-11-14 6:57 p.m., Nadav Amit wrote:
>> Eventually, if you get a fix into icecc, we will need to change the
>> Makefile, consider the version number and act accordingly.
> 
> I got a fix pulled into icecc[1] and it works quite well. It ought to be
> included in the next version of icecc. And distcc (with pump at least)
> has a patch too. In my experience, icecc does a much better job
> distributing the kernel build though.
> 
> Logan
> 
> [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ficecc%2Ficecream%2Fpull%2F430&amp;data=02%7C01%7Cnamit%40vmware.com%7C044d795be30143ae26ef08d65586953b%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C636790433884222635&amp;sdata=4h72yLjvOF29kcAC5CM7CB9ukH3HoALNUfgKA62E4Gs%3D&amp;reserved=0

Thanks for taking care of it. This change is certainly simpler and cleaner
than the one I came with.

So what’s your take? Would you think this patch is still needed? Should it
only be enabled automatically for distcc and not for distcc-pump?


  reply	other threads:[~2018-11-29  0:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 15:02 [PATCH 0/2] x86: Asm macros fixes Nadav Amit
2018-11-12 15:02 ` Nadav Amit
2018-11-12 15:02 ` [PATCH 1/2] Makefile: Fix distcc compilation with x86 macros Nadav Amit
2018-11-12 15:02   ` Nadav Amit
2018-11-13 11:30   ` Ingo Molnar
2018-11-13 17:55     ` Nadav Amit
2018-11-13 18:34       ` Nadav Amit
2018-11-14  7:29         ` Logan Gunthorpe
2018-11-14 17:46           ` Nadav Amit
2018-11-15  1:19             ` Logan Gunthorpe
2018-11-15  1:57               ` Nadav Amit
2018-11-15  2:00                 ` Logan Gunthorpe
2018-11-28 23:09                 ` Logan Gunthorpe
2018-11-29  0:38                   ` Nadav Amit [this message]
2018-11-29  0:49                     ` Logan Gunthorpe
2018-11-29  1:31                       ` Nadav Amit
2018-11-29 16:43                         ` Logan Gunthorpe
2018-12-01  6:29                           ` Nadav Amit
2018-11-12 15:02 ` [PATCH 2/2] x86: set a dependency on macros.S Nadav Amit
2018-11-12 15:02   ` Nadav Amit
2018-11-13 11:30   ` Ingo Molnar

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=5682CCB4-B7D3-4DDC-81BB-2D4DCE968A3D@vmware.com \
    --to=namit@vmware.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=michal.lkml@markovi.net \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --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.