From: David Howells <dhowells@redhat.com>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: dhowells@redhat.com, linux-mtd@lists.infradead.org,
akpm@linux-foundation.org, David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: add module license to mtdbdi
Date: Thu, 28 Jun 2007 08:21:08 +0100 [thread overview]
Message-ID: <1224.1183015268@redhat.com> (raw)
In-Reply-To: <200706272350.04975.m.kozlowski@tuxland.pl>
Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
> This seems to be a known issue [1] about Photron PNC-2000 module called
> pnc2000. To reproduce this just 'modprobe pnc2000'. The patch attached at least
> makes the kernel to be not tainted when mtdbdi gets loaded.
This is the wrong solution. This file should not be its own module, but
should rather be linked with mtdcore.
There was a patch for this, but I don't know what happened to it.
David
prev parent reply other threads:[~2007-06-28 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706271030.l5RAUgKE015163@imap1.linux-foundation.org>
2007-06-27 21:50 ` [PATCH] mtd: add module license to mtdbdi Mariusz Kozlowski
2007-06-28 7:21 ` David Howells [this message]
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=1224.1183015268@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=m.kozlowski@tuxland.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox