From: David Miller <davem@davemloft.net>
To: linus.luessing@web.de
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2 net-next] bridge: fix bugs introduced by last multicast patchset
Date: Thu, 12 Jun 2014 11:00:42 -0700 (PDT) [thread overview]
Message-ID: <20140612.110042.301380151424639820.davem@davemloft.net> (raw)
In-Reply-To: <1402530084-15061-1-git-send-email-linus.luessing@web.de>
From: Linus Lüssing <linus.luessing@web.de>
Date: Thu, 12 Jun 2014 01:41:22 +0200
> Once my last patchset got applied, I got slapped by an automatic smatch
> and build bot. Here are two patches fixing the according issues, a potential
> null pointer dereference and a compile error when compiling without IPv6.
Series applied, thanks.
prev parent reply other threads:[~2014-06-12 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 23:41 [PATCH 0/2 net-next] bridge: fix bugs introduced by last multicast patchset Linus Lüssing
2014-06-11 23:41 ` [PATCH 1/2] bridge: fix smatch warning / potential null pointer dereference Linus Lüssing
2014-06-11 23:41 ` [PATCH 2/2] bridge: fix compile error when compiling without IPv6 support Linus Lüssing
2014-06-12 18:00 ` 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=20140612.110042.301380151424639820.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=linus.luessing@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).