From: David Miller <davem@davemloft.net>
To: jim.epost@gmail.com
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
netdev@vger.kernel.org
Subject: Re: randconfig build error with next-20140109, in net/ipv6/ip6_vti.c
Date: Thu, 09 Jan 2014 15:58:27 -0500 (EST) [thread overview]
Message-ID: <20140109.155827.536194406324178452.davem@davemloft.net> (raw)
In-Reply-To: <CA+r1Zhg2srn3FkJcjKg0xiwbR89127sockdNQiGqUYn1qYTC0g@mail.gmail.com>
From: Jim Davis <jim.epost@gmail.com>
Date: Thu, 9 Jan 2014 06:55:50 -0700
> Building with the attached random configuration file,
I cannot reproduce this in either the 'net' or 'net-next' tree.
prev parent reply other threads:[~2014-01-09 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 13:55 randconfig build error with next-20140109, in net/ipv6/ip6_vti.c Jim Davis
2014-01-09 20:58 ` David Miller [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=20140109.155827.536194406324178452.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jim.epost@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=steffen.klassert@secunet.com \
--cc=yoshfuji@linux-ipv6.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