From: Artem Bityutskiy <dedekind@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Linux MTD <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch/rfc 2.6.29 2/2] MTD: support driver model updates
Date: Wed, 01 Apr 2009 08:46:11 +0300 [thread overview]
Message-ID: <1238564771.20906.26.camel@localhost.localdomain> (raw)
In-Reply-To: <200903260042.50236.david-b@pacbell.net>
On Thu, 2009-03-26 at 00:42 -0700, David Brownell wrote:
> From: David Brownell <dbrownell@users.sourceforge.net>
>
> Follow-on patch to the previous driver model patch for the MTD
> framework. This one makes various MTD drivers connect to the
> driver model tree, so /sys/devices/virtual/mtd/* nodes are no
> longer present ... mostly drivers used on boards I have handy.
>
> Based on a patch from Kay Sievers.
...
> --- a/drivers/mtd/nand/mxc_nand.c
> +++ b/drivers/mtd/nand/mxc_nand.c
> @@ -866,6 +866,7 @@ static int __init mxcnd_probe(struct pla
> mtd = &host->mtd;
> mtd->priv = this;
> mtd->owner = THIS_MODULE;
> + mtd->dev.parent = &pdev->dev;
Could this be done for all NANDs in nand_base.c instead?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [patch/rfc 2.6.29 2/2] MTD: support driver model updates
Date: Wed, 01 Apr 2009 08:46:11 +0300 [thread overview]
Message-ID: <1238564771.20906.26.camel@localhost.localdomain> (raw)
In-Reply-To: <200903260042.50236.david-b@pacbell.net>
On Thu, 2009-03-26 at 00:42 -0700, David Brownell wrote:
> From: David Brownell <dbrownell@users.sourceforge.net>
>
> Follow-on patch to the previous driver model patch for the MTD
> framework. This one makes various MTD drivers connect to the
> driver model tree, so /sys/devices/virtual/mtd/* nodes are no
> longer present ... mostly drivers used on boards I have handy.
>
> Based on a patch from Kay Sievers.
...
> --- a/drivers/mtd/nand/mxc_nand.c
> +++ b/drivers/mtd/nand/mxc_nand.c
> @@ -866,6 +866,7 @@ static int __init mxcnd_probe(struct pla
> mtd = &host->mtd;
> mtd->priv = this;
> mtd->owner = THIS_MODULE;
> + mtd->dev.parent = &pdev->dev;
Could this be done for all NANDs in nand_base.c instead?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-04-01 5:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903260039.34013.david-b@pacbell.net>
2009-03-26 7:42 ` [patch/rfc 2.6.29 2/2] MTD: support driver model updates David Brownell
2009-04-01 5:46 ` Artem Bityutskiy [this message]
2009-04-01 5:46 ` Artem Bityutskiy
2009-04-01 5:57 ` David Brownell
2009-04-01 5:57 ` David Brownell
2009-04-01 6:10 ` Artem Bityutskiy
2009-04-01 6:10 ` Artem Bityutskiy
2009-04-01 6:42 ` David Brownell
2009-04-01 6:42 ` David Brownell
2009-04-01 6:48 ` Artem Bityutskiy
2009-04-01 6:48 ` Artem Bityutskiy
2009-04-01 6:08 ` Vitaly Wool
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=1238564771.20906.26.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=david-b@pacbell.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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.