From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754768Ab2CSVOt (ORCPT ); Mon, 19 Mar 2012 17:14:49 -0400 Received: from perches-mx.perches.com ([206.117.179.246]:60432 "EHLO labridge.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752810Ab2CSVOs (ORCPT ); Mon, 19 Mar 2012 17:14:48 -0400 Message-ID: <1332191687.6525.15.camel@joe2Laptop> Subject: Re: [PATCH net-next] net: ipv4: Standardize prefixes for message logging From: Joe Perches To: David Miller Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Date: Mon, 19 Mar 2012 14:14:47 -0700 In-Reply-To: <20120319.170349.957038489849471796.davem@davemloft.net> References: <20120312.170558.584205292599435892.davem@davemloft.net> <1331598952.13200.43.camel@joe2Laptop> <1332190804.6525.12.camel@joe2Laptop> <20120319.170349.957038489849471796.davem@davemloft.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.2- Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-03-19 at 17:03 -0400, David Miller wrote: > From: Joe Perches > Date: Mon, 19 Mar 2012 14:00:04 -0700 [] > > Would you still take a similar IPv6: prefix > > change for net-next or should I wait until > > the next release cycle? > Sure why not, [] > Instead, it really means "too late." No worries, I'll set a good example instead.