public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft•net>
To: gorcunov@gmail•com
Cc: randy.dunlap@oracle•com, pablo@netfilter•org,
	sfr@canb•auug.org.au, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
	kaber@trash•net, netfilter-devel@vger•kernel.org
Subject: Re: linux-next: Tree for March 27 (netfilter build error)
Date: Sat, 28 Mar 2009 23:47:39 -0700 (PDT)	[thread overview]
Message-ID: <20090328.234739.26481917.davem@davemloft.net> (raw)
In-Reply-To: <20090329064704.GA7255@localhost>

From: Cyrill Gorcunov <gorcunov@gmail•com>
Date: Sun, 29 Mar 2009 10:47:04 +0400

> [Randy Dunlap - Sat, Mar 28, 2009 at 09:26:42PM -0700]
> ... 
> | works_for_me.  Thanks.
> | but missing S-O-B.
> | 
> | Acked-by: Randy Dunlap <randy.dunlap@oracle•com>
> ...
> 
> Thanks for testing Randy. So if nobody will complain
> here is a solid version of the patch. Though I would like
> if Pablo or Patrick confirm its correctness. Thanks!

I'll apply this once Patrick or Pablo have a look at it.

Thanks.

  reply	other threads:[~2009-03-29  6:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 12:19 linux-next: Tree for March 27 Stephen Rothwell
2009-03-27 13:57 ` Next March 27 : s390 defconfig build failure Sachin Sant
2009-03-27 14:40   ` Heiko Carstens
2009-03-30  9:51     ` Sachin Sant
2009-03-27 16:48 ` linux-next: Tree for March 27 (netfilter build error) Randy Dunlap
2009-03-27 23:01   ` David Miller
2009-03-28 10:28     ` Cyrill Gorcunov
2009-03-29  4:26       ` Randy Dunlap
2009-03-29  6:47         ` Cyrill Gorcunov
2009-03-29  6:47           ` David Miller [this message]
2009-03-29 11:48             ` Harald Welte
2009-03-29 11:59             ` Pablo Neira Ayuso
2009-03-29 12:27               ` Cyrill Gorcunov
2009-03-29 20:46               ` David Miller
2009-03-30 12:00                 ` Patrick McHardy
2009-03-27 17:42 ` linux-next: Tree for March 27 (longhaul " Bartlomiej Zolnierkiewicz
2009-03-27 20:44   ` Len Brown

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=20090328.234739.26481917.davem@davemloft.net \
    --to=davem@davemloft$(echo .)net \
    --cc=gorcunov@gmail$(echo .)com \
    --cc=kaber@trash$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=netfilter-devel@vger$(echo .)kernel.org \
    --cc=pablo@netfilter$(echo .)org \
    --cc=randy.dunlap@oracle$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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