All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Rui Rui <ruirui.r.yang@tieto.com>
To: "Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>
Cc: Yang Ruirui R <ruirui.r.yang@tietoenator.com>,
	"ext-phil.2.carmody@nokia.com" <ext-phil.2.carmody@nokia.com>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"ext-jani.1.nikula@nokia.com" <ext-jani.1.nikula@nokia.com>
Subject: Re: [PATCH 02/02] force module loaded with partitions set
Date: Thu, 17 Mar 2011 16:50:06 +0800	[thread overview]
Message-ID: <4D81CB3E.9030001@tieto.com> (raw)
In-Reply-To: <1300095199.2727.10.camel@localhost>

On 03/14/2011 05:33 PM, Artem Bityutskiy wrote:
> On Mon, 2011-03-14 at 17:12 +0800, Yang Rui Rui wrote:
>>> I think you should rather re-work the framework a bit and make the
>>> "->add_mtd()" call-back return an integer error code. Then we could just
>>> return errors on error and prevent the module from being loaded.
>>>
>>
>> I'm thinking is it possible to pass partitions param later? ie. use sysfs attribute?
>
> It may be possible, but would probably require some work.
>

mainline mtd & mtd_blkdev changes a lot since 2.6.32, but there's no
way for me to test with linux-mtd tree due to lack real hardware.

work on this with 2.6.32 seems not so necessary,
So I think I will give up, sorry about that.

-- 
Thanks
Yang Ruirui

  reply	other threads:[~2011-03-17  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14  1:51 [PATCH 02/02] force module loaded with partitions set Yang Ruirui
2011-03-14  8:43 ` Artem Bityutskiy
2011-03-14  8:57   ` Yang Rui Rui
2011-03-14  8:53     ` Artem Bityutskiy
2011-03-14  9:12       ` Yang Rui Rui
2011-03-14  9:33         ` Artem Bityutskiy
2011-03-17  8:50           ` Yang Rui Rui [this message]
2011-03-17  8:51             ` Artem Bityutskiy
2011-03-17  9:24               ` Yang Rui Rui

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=4D81CB3E.9030001@tieto.com \
    --to=ruirui.r.yang@tieto.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=dwmw2@infradead.org \
    --cc=ext-jani.1.nikula@nokia.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ruirui.r.yang@tietoenator.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.