netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: remove silly double assignment
Date: Mon, 29 Oct 2012 10:21:04 +0900	[thread overview]
Message-ID: <20121029012103.GF26847@verge.net.au> (raw)
In-Reply-To: <20121028225349.GB1143@1984>

On Sun, Oct 28, 2012 at 11:53:49PM +0100, Pablo Neira Ayuso wrote:
> On Fri, Oct 26, 2012 at 11:13:27AM +0100, Alan Cox wrote:
> > From: Alan Cox <alan@linux.intel.com>
> > 
> > I don't even want to think what the C spec says for this 8)
> 
> I don't want to know it either :-), I have applied this.
> 
> @Simon: this patch is fairly small, I'll take it myself into nf-next.

Thanks.

      reply	other threads:[~2012-10-29  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 10:13 [PATCH] netfilter: remove silly double assignment Alan Cox
2012-10-28 22:53 ` Pablo Neira Ayuso
2012-10-29  1:21   ` Simon Horman [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=20121029012103.GF26847@verge.net.au \
    --to=horms@verge.net.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).