All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: sedat.dilek@gmail.com
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [next-20110214] Kernel-modules with unknown parameter
Date: Tue, 15 Feb 2011 10:30:26 +1030	[thread overview]
Message-ID: <201102151030.26956.rusty@rustcorp.com.au> (raw)
In-Reply-To: <AANLkTinFOPc+BM8cnPE3SLt7Dc2TFOw1v+bntFu01hpO@mail.gmail.com>

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.

  parent reply	other threads:[~2011-02-15  0:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 12:13 [next-20110214] Kernel-modules with unknown parameter Sedat Dilek
2011-02-14 12:24 ` Sedat Dilek
2011-02-14 12:24   ` Sedat Dilek
2011-02-14 13:15   ` Sedat Dilek
2011-02-14 15:32     ` Sedat Dilek
2011-02-15  0:00     ` Rusty Russell [this message]
2011-02-15  3:34       ` Sedat Dilek
2011-02-15  3:58         ` Stephen Rothwell
2011-02-15  4:14           ` Sedat Dilek
2011-02-15  4:36             ` Dmitry Torokhov
2011-02-15  8:39               ` Sedat Dilek

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=201102151030.26956.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.