From: Michal Marek <mmarek@suse.com>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/6] deb-pkg: Remove the KBUILD_IMAGE workaround
Date: Fri, 25 Nov 2016 15:22:22 +0100 [thread overview]
Message-ID: <5dd95503-9782-6c9a-a6ac-6067eed1935e@suse.com> (raw)
In-Reply-To: <CAAqcGHmnGFgCjmsjerecy2Jf0YaCThGp5TxS1yNXqGzZnsXLBQ@mail.gmail.com>
Dne 25.11.2016 v 13:12 Riku Voipio napsal(a):
> On 22 November 2016 at 23:34, Michal Marek <mmarek@suse.com> wrote:
>> The arch Makefile are fixed to set KBUILD_IMAGE to the full patch, so
>> the workaround is no longer needed.
>>
>> Signed-off-by: Michal Marek <mmarek@suse.com>
>> ---
> Thanks for cleaning this up.
>
> Reviewed-by: Riku Voipio <riku.voipio@linaro.org>
Note that this will only be merged once the individual arch patches have
been picked up.
Michal
next prev parent reply other threads:[~2016-11-25 14:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 21:34 [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition Michal Marek
2016-11-22 21:34 ` [PATCH 2/6] arm: " Michal Marek
2017-03-20 13:53 ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 3/6] arc: " Michal Marek
2016-11-23 19:40 ` Alexey Brodkin
2016-11-25 14:21 ` Michal Marek
2017-03-20 13:54 ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 4/6] sh: " Michal Marek
2017-03-20 13:54 ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 5/6] unicore32: " Michal Marek
2017-03-20 13:55 ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 6/6] deb-pkg: Remove the KBUILD_IMAGE workaround Michal Marek
2016-11-25 12:12 ` Riku Voipio
2016-11-25 14:22 ` Michal Marek [this message]
2017-03-20 13:56 ` Masahiro Yamada
2017-03-10 17:58 ` [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition Will Deacon
2017-03-10 21:20 ` Michal Marek
2017-03-18 13:14 ` Masahiro Yamada
2017-03-20 12:13 ` Will Deacon
2017-03-20 13:52 ` 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=5dd95503-9782-6c9a-a6ac-6067eed1935e@suse.com \
--to=mmarek@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@linaro.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 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®