From: Michael Wang <yun.wang@profitbricks.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: nfnetlink warnings
Date: Mon, 23 Nov 2015 11:36:34 +0100 [thread overview]
Message-ID: <5652EC32.4020902@profitbricks.com> (raw)
In-Reply-To: <20151123103212.GD5134@pd.tnic>
On 11/23/2015 11:32 AM, Borislav Petkov wrote:
> On Mon, Nov 23, 2015 at 11:20:18AM +0100, Michael Wang wrote:
>> Who want to do that would take responsibility to make an else branch at
>> that time, but reserve the branch at this moment sounds unnecessary, and
>> not that pretty frankly speaking.
>
> Actually, I was looking for the better idea which doesn't uglify the
> code. And here it is:
>
> https://lkml.kernel.org/r/5585663.OcpAQiytKY@wuerfel
Looks even better :-)
Regards,
Michael Wang
>
> :-)
>
prev parent reply other threads:[~2015-11-23 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 9:36 nfnetlink warnings Borislav Petkov
2015-11-23 9:36 ` Borislav Petkov
2015-11-23 9:49 ` Michael Wang
2015-11-23 9:54 ` Borislav Petkov
2015-11-23 10:20 ` Michael Wang
2015-11-23 10:30 ` Pablo Neira Ayuso
2015-11-23 10:32 ` Borislav Petkov
2015-11-23 10:36 ` Michael Wang [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=5652EC32.4020902@profitbricks.com \
--to=yun.wang@profitbricks.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.