linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, James Morris <jmorris@namei.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Woodhouse <David.Woodhouse@intel.com>
Subject: Re: linux-next: build failure after merge of the security tree
Date: Wed, 26 Aug 2015 15:45:05 +0100	[thread overview]
Message-ID: <15177.1440600305@warthog.procyon.org.uk> (raw)
In-Reply-To: <20150817160458.0c2bb25a@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> > After a bit of digging, I installed libssl-dev on my Debian build
> > machines.
> 
> Is this worth a mention in Documentation/Changes along with all the
> other prerequisites?

Could be.  It's mentioned in the Kconfig and Documentation/module-signing.txt
already, but this looks like a good place.

David

  parent reply	other threads:[~2015-08-26 14:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17  5:29 linux-next: build failure after merge of the security tree Stephen Rothwell
2015-08-17  6:04 ` Stephen Rothwell
2015-08-26 14:45 ` David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-08  4:00 Stephen Rothwell
2020-07-13  2:04 ` Stephen Rothwell
2020-07-13  2:06   ` Stephen Rothwell
2020-07-29 23:35   ` Stephen Rothwell
2020-07-30  2:35     ` James Morris
2020-07-30  2:59       ` Stephen Rothwell
2020-07-30  5:03         ` Stephen Rothwell
2020-08-04  3:36         ` James Morris
2019-08-12  4:58 Stephen Rothwell
2019-08-12 17:34 ` Kees Cook
2019-08-19  3:21   ` Stephen Rothwell
2019-08-19  3:38     ` Stephen Rothwell
2019-08-21 16:39     ` James Morris
2017-08-23 11:12 Stephen Rothwell
2017-08-17  2:51 Stephen Rothwell
2017-08-17  3:24 ` Kees Cook
2016-05-19  4:01 Stephen Rothwell
     [not found] ` <20160519140120.23b345a1-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2016-05-19 10:11   ` David Howells
2016-05-19 23:14   ` Stephen Rothwell
2016-05-20  3:07     ` Steve French
2014-07-25  9:21 Stephen Rothwell

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=15177.1440600305@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=David.Woodhouse@intel.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.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;
as well as URLs for NNTP newsgroup(s).