All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-mtd@lists.infradead.org, Erez Zadok <ezk@cs.sunysb.edu>,
	dwmw2@infradead.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block2mtd lockdep_init_map warning
Date: Sun, 06 Jan 2008 14:39:22 +0100	[thread overview]
Message-ID: <1199626763.31975.50.camel@lappy> (raw)
In-Reply-To: <20080106131343.GA3120@lazybastard.org>


On Sun, 2008-01-06 at 14:13 +0100, Jörn Engel wrote:

> Ingo, Peter, does either of you actually care about this problem?  In
> the last round when I debugged this problem there was a notable lack of
> reaction from either of you.

Yeah I do, I just know very little about the module stuff and haven't
come around to looking into it.

I agree that Erez's patch is quite horrible.

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: Erez Zadok <ezk@cs.sunysb.edu>,
	dwmw2@infradead.org, linux-mtd@lists.infradead.org,
	mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block2mtd lockdep_init_map warning
Date: Sun, 06 Jan 2008 14:39:22 +0100	[thread overview]
Message-ID: <1199626763.31975.50.camel@lappy> (raw)
In-Reply-To: <20080106131343.GA3120@lazybastard.org>


On Sun, 2008-01-06 at 14:13 +0100, Jörn Engel wrote:

> Ingo, Peter, does either of you actually care about this problem?  In
> the last round when I debugged this problem there was a notable lack of
> reaction from either of you.

Yeah I do, I just know very little about the module stuff and haven't
come around to looking into it.

I agree that Erez's patch is quite horrible.


  reply	other threads:[~2008-01-06 13:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  7:17 [PATCH] block2mtd lockdep_init_map warning Erez Zadok
2008-01-06 13:13 ` Jörn Engel
2008-01-06 13:13   ` Jörn Engel
2008-01-06 13:39   ` Peter Zijlstra [this message]
2008-01-06 13:39     ` Peter Zijlstra
2008-01-06 19:11   ` Erez Zadok
2008-01-06 19:11     ` Erez Zadok
2008-01-06 21:25     ` Jörn Engel
2008-01-06 21:25       ` Jörn Engel
2008-01-07 10:05     ` Peter Zijlstra
2008-01-07 10:05       ` Peter Zijlstra
2008-01-07 10:20       ` Jörn Engel
2008-01-07 10:20         ` Jörn Engel
2008-01-07 10:34         ` Peter Zijlstra
2008-01-07 10:34           ` Peter Zijlstra
2008-01-08  0:47       ` Rusty Russell
2008-01-08  0:47         ` Rusty Russell
2008-01-16  8:16         ` Peter Zijlstra
2008-01-16  8:16           ` Peter Zijlstra
2008-01-16 21:20         ` Jörn Engel
2008-01-16 21:20           ` Jörn Engel
2008-01-20 21:01           ` Erez Zadok
2008-01-20 21:01             ` Erez Zadok

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=1199626763.31975.50.camel@lappy \
    --to=peterz@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mingo@redhat.com \
    /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.