From: <yamada.masahiro@socionext.com>
To: <aik@ozlabs.ru>, <linux-kbuild@vger.kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
michal.lkml@markovi.net, keescook@chromium.org,
maurosr@linux.vnet.ibm.com, jhogan@kernel.org,
ralf@linux-mips.org, x86@kernel.org, mgreer@animalcreek.com,
npiggin@gmail.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, paul.burton@mips.com, mingo@redhat.com,
paulus@samba.org, joel@jms.id.au, hpa@zytor.com, bp@alien8.de,
tglx@linutronix.de, linux-mips@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: RE: [PATCH 2/3] kbuild: add real-prereqs shorthand for $(filter-out FORCE, $^)
Date: Thu, 17 Jan 2019 05:59:03 +0000 [thread overview]
Message-ID: <bf7380ec3fa145958c3f7b3e3551a395@SOC-EX01V.e01.socionext.com> (raw)
In-Reply-To: <71a0e80a-c587-4973-cfc3-9c74b2b3a16c@ozlabs.ru>
Hi Alexey,
> What is this series made on top of? This does not apply on top of master
> from
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
If you want to apply this series cleanly, please apply the following first:
https://patchwork.kernel.org/patch/10761625/
https://patchwork.kernel.org/patch/10767193/
The conflicts are not significant.
You can use 'git am -C1' if you want to apply this series
directly to Linus tree.
Masahiro
prev parent reply other threads:[~2019-01-17 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1547698231-20985-1-git-send-email-yamada.masahiro@socionext.com>
2019-01-17 4:10 ` [PATCH 2/3] kbuild: add real-prereqs shorthand for $(filter-out FORCE, $^) Masahiro Yamada
2019-01-17 4:22 ` Alexey Kardashevskiy
2019-01-17 5:59 ` yamada.masahiro [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=bf7380ec3fa145958c3f7b3e3551a395@SOC-EX01V.e01.socionext.com \
--to=yamada.masahiro@socionext.com \
--cc=aik@ozlabs.ru \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=jhogan@kernel.org \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=maurosr@linux.vnet.ibm.com \
--cc=mgreer@animalcreek.com \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=paul.burton@mips.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox