From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller 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) Message-ID: <20140612.110042.301380151424639820.davem@davemloft.net> References: <1402530084-15061-1-git-send-email-linus.luessing@web.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: stephen@networkplumber.org, netdev@vger.kernel.org, bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org To: linus.luessing@web.de Return-path: In-Reply-To: <1402530084-15061-1-git-send-email-linus.luessing@web.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: bridge-bounces@lists.linux-foundation.org Errors-To: bridge-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org From: Linus L=FCssing Date: Thu, 12 Jun 2014 01:41:22 +0200 > Once my last patchset got applied, I got slapped by an automatic smat= ch > and build bot. Here are two patches fixing the according issues, a po= tential > null pointer dereference and a compile error when compiling without I= Pv6. Series applied, thanks.