Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932332Ab3HGQN3 (ORCPT ); Wed, 7 Aug 2013 12:13:29 -0400 Received: from s3.sipsolutions.net ([144.76.43.152]:59841 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932222Ab3HGQNZ (ORCPT ); Wed, 7 Aug 2013 12:13:25 -0400 Message-ID: <1375891974.8154.1.camel@jlt4.sipsolutions.net> Subject: Re: linux-next: Tree for Aug 7 From: Johannes Berg To: Phil Sutter Cc: Sedat Dilek , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, David Miller , Hannes Frederic Sowa , wireless , John Linville Date: Wed, 07 Aug 2013 18:12:54 +0200 In-Reply-To: <20130807155918.GA16263@orbit.nwl.cc> References: <20130807155443.a0355d0429f3e0b4ccbed261@canb.auug.org.au> <20130807155918.GA16263@orbit.nwl.cc> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 637 Lines: 16 On Wed, 2013-08-07 at 17:59 +0200, Phil Sutter wrote: > The idea behind this patch is that users setting the protocol to > something else probably do know better and so should be left alone. Regardless of that, I think that still the skb pointers would be changed by this patch which would confuse the receiver of the SKB (device driver), no? Has anyone verified that theory? :) johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/