public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Michal Marek <mmarek@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-kbuild@vger.kernel.org, Emese Revfy <re.emese@gmail.com>
Subject: Re: [PATCH] kbuild/builddeb: Fix !CONFIG_GCC_PLUGINS build
Date: Mon, 5 Sep 2016 09:45:24 +0200	[thread overview]
Message-ID: <20160905074524.GA18856@pd.tnic> (raw)
In-Reply-To: <57CD12D5.8040305@suse.com>

On Mon, Sep 05, 2016 at 08:38:13AM +0200, Michal Marek wrote:
> A fix has already been submitted by Kees Cook. I took your patch as a
> reminder to submit my rc-fixes branch to Linus :).

So it wasn't for nothing after all :-)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

      reply	other threads:[~2016-09-05  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03 19:58 [PATCH] kbuild/builddeb: Fix !CONFIG_GCC_PLUGINS build Borislav Petkov
2016-09-05  6:38 ` Michal Marek
2016-09-05  7:45   ` Borislav Petkov [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=20160905074524.GA18856@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=re.emese@gmail.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