kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [digsig:next-ima-module 13/36] {standard input}:5: Error: file not found: pubkey.pem.bin
Date: Fri, 03 Aug 2012 23:44:07 +0000	[thread overview]
Message-ID: <1344037447.2742.17.camel@falcor> (raw)

On Sat, 2012-08-04 at 07:08 +0800, Fengguang Wu wrote:
> Hi Mimi,
> 
> Kernel build failed on
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/kasatkin/linux-digsig.git next-ima-module
> head:   31baf831da8f67a11c14de7989bf68551396b356
> commit: d396af8b7f5b9a72b15470284ca13aac1372e9d9 [13/36] integrity: create and inititialize a keyring with builtin public key
> config: x86_64-allmodconfig (attached as .config)
> 
> Build errors:
> 
> {standard input}:5: Error: file not found: pubkey.pem.bin

Hi Fengguang,

Congratulations on receiving an invitation to the kernel summit!

I really appreciate your running tests on the different trees, but
Dmitry and I are still working on the next-ima-modules and
next-ima-directory branches.  Instead of pushing out a branch to show
Dmitry the patches, I sent him a tar, so that I wouldn't get dinged for
build issues.  We haven't finalized the patch content or ordering yet.

We need some sort of mechanism that allows us to collaborate.  What do
you think if Dmitry and I suffix a branch with 'test' until we're ready?

thanks,

Mimi


             reply	other threads:[~2012-08-03 23:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 23:44 Mimi Zohar [this message]
2012-08-03 23:53 ` [digsig:next-ima-module 13/36] {standard input}:5: Error: file not found: pubkey.pem.bin Fengguang Wu

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=1344037447.2742.17.camel@falcor \
    --to=zohar@linux.vnet.ibm.com \
    --cc=kernel-janitors@vger.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;
as well as URLs for NNTP newsgroup(s).