From: David Howells <dhowells@redhat.com>
To: Chun-Yi Lee <joeyli.kernel@gmail.com>
Cc: dhowells@redhat.com, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org, Chun-Yi Lee <jlee@suse.com>,
Josh Boyer <jwboyer@redhat.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>,
Michal Marek <mmarek@suse.com>
Subject: Re: [PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists
Date: Thu, 21 Feb 2013 14:16:05 +0000 [thread overview]
Message-ID: <804.1361456165@warthog.procyon.org.uk> (raw)
In-Reply-To: <1361445829-23594-1-git-send-email-jlee@suse.com>
> +ifneq ($(shell pwd), $(srctree))
How reliable is this, I wonder?
David
next prev parent reply other threads:[~2013-02-21 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 11:23 [PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists Chun-Yi Lee
2013-02-21 14:16 ` David Howells [this message]
2013-02-22 8:38 ` joeyli
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=804.1361456165@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=jlee@suse.com \
--cc=joeyli.kernel@gmail.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=rdunlap@xenotime.net \
--cc=rusty@rustcorp.com.au \
/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