From: Tom Rini <trini@konsulko.com>
To: Michal Marek <mmarek@suse.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: kbuild/mkspec: Fix architectures where KBUILD_IMAGE isn't a full path
Date: Wed, 15 Mar 2017 11:37:55 -0400 [thread overview]
Message-ID: <20170315153755.GR19897@bill-the-cat> (raw)
In-Reply-To: <39bd8ad9-ce11-3d81-95a9-235ceaded812@suse.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Wed, Mar 15, 2017 at 04:03:44PM +0100, Michal Marek wrote:
> Dne 15.3.2017 v 15:51 Tom Rini napsal(a):
> > I found https://patchwork.kernel.org/patch/9442211/ today and I see that
> > it was brought up again just before I sent my patch. I just want to
> > point out that 9442211 doesn't address arm, arc, and sh and they will
> > still not have a functional rpm build target. This is at least probably
> > important for arm. Of course all of those could also be addressed with
> > a patch similar to 9442211, and my main concern is making sure
> > everything gets fixed one way or another. Thanks!
>
> The patch is 1/6 of a series that also covers other architectures, but
> patchwork won't should you the rest of the thread. Have a look here for
> instance: https://lkml.org/lkml/2016/11/22/750.
Ah, OK, thanks. I'll just hope it gets in soon, I like being able to
easily drop new kernels in on my arm64 box :)
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-03-15 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 23:59 [PATCH] " Tom Rini
2017-03-15 14:51 ` Tom Rini
2017-03-15 15:03 ` Michal Marek
2017-03-15 15:37 ` Tom Rini [this message]
2017-03-20 10:13 ` Will Deacon
2017-03-20 17:00 ` Masahiro Yamada
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=20170315153755.GR19897@bill-the-cat \
--to=trini@konsulko.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®