Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753867Ab1BOAAc (ORCPT ); Mon, 14 Feb 2011 19:00:32 -0500 Received: from ozlabs.org ([203.10.76.45]:44166 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751997Ab1BOAA3 (ORCPT ); Mon, 14 Feb 2011 19:00:29 -0500 From: Rusty Russell To: sedat.dilek@gmail.com Subject: Re: [next-20110214] Kernel-modules with unknown parameter Date: Tue, 15 Feb 2011 10:30:26 +1030 User-Agent: KMail/1.13.5 (Linux/2.6.35-25-generic; KDE/4.5.1; i686; ; ) Cc: linux-next@vger.kernel.org, LKML , Stephen Rothwell , Randy Dunlap , Dmitry Torokhov References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201102151030.26956.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 750 Lines: 21 On Mon, 14 Feb 2011 11:45:59 pm Sedat Dilek wrote: > >> Any idea what's going on? Stephen, Randy noticed the same like me? Dmitry broke module parameters with a "trivial" transform which turned out not to be. I wasn't paying enough attention, and let it through. > My damn brain can't understand - looking at the series file in [2] - > why the hell the "possible" patch [3] is not included in linux-next? There are markers in the series file, which indicate what goes into linux-next. Cheers, Rusty. -- 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/