public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg-63ez5xqkn6DQT0dZR+AlfA@public.gmane.org>
To: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	drbd-dev-cunTk1MwBs8qoQakbn7OcQ@public.gmane.org
Subject: Re: linux-next: Tree for Feb 23 (drbd)
Date: Fri, 1 Mar 2013 13:34:16 +0100	[thread overview]
Message-ID: <20130301123416.GO2696@soda.linbit> (raw)
In-Reply-To: <512BBB43.8060309-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

On Mon, Feb 25, 2013 at 11:28:03AM -0800, Randy Dunlap wrote:
> On 02/24/13 21:00, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Please do not add any work destined for v3.10 to your -next included
> > branches until after Linus has release v3.9-rc1.
> > 
> > Changes since 20130222:
> > 
> 
> 
> on i386:
> 
>   CC [M]  drivers/block/drbd/drbd_receiver.o
> drivers/block/drbd/drbd_receiver.c: In function 'drbd_do_auth':
> drivers/block/drbd/drbd_receiver.c:4662:10: error: 'mdev' undeclared (first use in this function)
> make[4]: *** [drivers/block/drbd/drbd_receiver.o] Error 1
> 
> 
> Full randconfig file is attached.

see: https://lkml.org/lkml/2013/2/5/375
and:
http://git.drbd.org/gitweb.cgi?p=linux-drbd.git;a=commitdiff;h=23c275cba16615ac8cd3815cb1a86fd64cf12aa6

> # CONFIG_CRYPTO_HMAC is not set

	Lars

      parent reply	other threads:[~2013-03-01 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  5:00 linux-next: Tree for Feb 23 Stephen Rothwell
2013-02-25 19:28 ` linux-next: Tree for Feb 23 (drbd) Randy Dunlap
     [not found]   ` <512BBB43.8060309-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-03-01 12:34     ` Lars Ellenberg [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=20130301123416.GO2696@soda.linbit \
    --to=lars.ellenberg-63ez5xqkn6dqt0dzr+alfa@public.gmane.org \
    --cc=drbd-dev-cunTk1MwBs8qoQakbn7OcQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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