All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: kaber@trash.net, justinmattock@gmail.com, eric.dumazet@gmail.com,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, horms@verge.net.au,
	netfilter-devel@vger.kernel.org
Subject: Re: error while building the kernel Mainline
Date: Thu, 18 Nov 2010 13:03:18 -0800	[thread overview]
Message-ID: <20101118130318.073f6beb.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101118.125451.98885354.davem@davemloft.net>

On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:

> From: Patrick McHardy <kaber@trash.net>
> Date: Thu, 18 Nov 2010 21:32:11 +0100
> 
> > Thanks for testing. Dave, please apply directly, thanks!

Dave,

This patch does not fix the config/build error that I posted for linux-next.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-11-18 21:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 14:36 error while building the kernel Mainline Justin Mattock
2010-11-18 15:12 ` Eric Dumazet
2010-11-18 17:25   ` Justin P. Mattock
2010-11-18 17:48     ` Eric Dumazet
2010-11-18 17:48       ` Eric Dumazet
2010-11-18 17:50       ` David Miller
2010-11-18 18:12         ` Patrick McHardy
2010-11-18 18:13         ` Justin P. Mattock
2010-11-18 18:20           ` Patrick McHardy
2010-11-18 18:28             ` Justin P. Mattock
2010-11-18 19:18             ` Justin P. Mattock
2010-11-18 20:32               ` Patrick McHardy
2010-11-18 20:54                 ` David Miller
2010-11-18 21:03                   ` Randy Dunlap [this message]
2010-11-18 21:10                     ` David Miller
2010-11-18 21:15                       ` David Miller
2010-11-18 21:48                         ` Patrick McHardy
2010-11-18 23:48                           ` Justin P. Mattock
2010-11-19  0:20                             ` Simon Horman

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=20101118130318.073f6beb.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@verge.net.au \
    --cc=justinmattock@gmail.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.