From: Michal Marek <mmarek@suse.com>
To: Kees Cook <keescook@chromium.org>
Cc: Frank Paulsen <frobnic+lkml@gmail.com>,
Christian Kujau <lists@nerdbynature.de>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] builddeb: Skip gcc-plugins when not configured
Date: Tue, 16 Aug 2016 10:34:41 +0200 [thread overview]
Message-ID: <57B2D021.9010402@suse.com> (raw)
In-Reply-To: <20160815173622.GA24820@www.outflux.net>
Dne 15.8.2016 v 19:36 Kees Cook napsal(a):
> When attempting to build a Debian kernel package, the "scripts/gcc-plugins"
> directory does not exist in the output tree unless CONFIG_GCC_PLUGINS=y.
> To avoid errors when not defined, this wraps the failing "find" in a config
> test.
>
> Reported-by: Frank Paulsen <frobnic+lkml@gmail.com>
> Tested-by: Christian Kujau <lists@nerdbynature.de>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> This should go into v4.8...
Applied to kbuild.git#rc-fixes.
Thanks,
Michal
prev parent reply other threads:[~2016-08-16 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 17:36 [PATCH] builddeb: Skip gcc-plugins when not configured Kees Cook
2016-08-16 8:34 ` Michal Marek [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=57B2D021.9010402@suse.com \
--to=mmarek@suse.com \
--cc=frobnic+lkml@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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;
as well as URLs for NNTP newsgroup(s).