public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic•com>
Cc: Nicholas Piggin <npiggin@gmail•com>,
	Borislav Petkov <bp@alien8•de>,
	linux-next@vger•kernel.org, X86 ML <x86@kernel•org>,
	Steven Rostedt <rostedt@goodmis•org>,
	Adam Borowski <kilobyte@angband•pl>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: linux-next x86 build fixes
Date: Thu, 15 Dec 2016 07:41:51 +1100	[thread overview]
Message-ID: <20161215074151.2412ddb8@canb.auug.org.au> (raw)
In-Reply-To: <CAB=NE6XSPhQsjXNPhfuUjjHruBvxt-EF5q4N_Lu2ndz5Uo7_qQ@mail.gmail.com>

Hi Luis,

On Wed, 14 Dec 2016 11:17:25 -0600 "Luis R. Rodriguez" <mcgrof@do-not-panic•com> wrote:
>
> Curious if the x86 symbol build issues are supposed to be resolved
> already on linux-next as of today, if not, how's it looking to get
> this fixed ? I am carrying around Adam's temporary patch "kbuild:
> provide include/asm/asm-prototypes.h for x86" on top of linux-next but
> each day I move on I keep seeing this is still not fixed and keep
> having to carry it. Curious what the delays are to get this resolved,
> the last thread I saw seemed to acknowledge the issue and that Nick
> was working on a fix ?

That commit will be in linux-next today (it was added to the kbuild
tree last night (my time)).

-- 
Cheers,
Stephen Rothwell

      reply	other threads:[~2016-12-14 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 17:17 linux-next x86 build fixes Luis R. Rodriguez
2016-12-14 20:41 ` Stephen Rothwell [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=20161215074151.2412ddb8@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=bp@alien8$(echo .)de \
    --cc=kilobyte@angband$(echo .)pl \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mcgrof@do-not-panic$(echo .)com \
    --cc=npiggin@gmail$(echo .)com \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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