From: David Miller <davem@davemloft.net>
To: bcrl@kvack.org
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/l2tp: fix build error in l2tp from missing ipv6 checksum include
Date: Mon, 30 Apr 2012 13:31:48 -0400 (EDT) [thread overview]
Message-ID: <20120430.133148.1694639055532709407.davem@davemloft.net> (raw)
In-Reply-To: <20120430172402.GL17021@kvack.org>
From: Benjamin LaHaise <bcrl@kvack.org>
Date: Mon, 30 Apr 2012 13:24:02 -0400
> Can you please verify if the patch below fixes the issue? Thanks.
I already checked a fix into the tree.
prev parent reply other threads:[~2012-04-30 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 5:58 linux-next: build failure after merge of the final tree (net-next tree related) Stephen Rothwell
2012-04-30 17:22 ` David Miller
2012-04-30 17:24 ` [PATCH net-next] net/l2tp: fix build error in l2tp from missing ipv6 checksum include Benjamin LaHaise
2012-04-30 17:31 ` 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=20120430.133148.1694639055532709407.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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).