From: Vitaly Wool <vwool@ru.mvista.com>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
kernel list <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [patch] switch mtd to new driver model & cleanups
Date: Fri, 30 Sep 2005 22:12:32 +0400 [thread overview]
Message-ID: <433D8010.1090701@ru.mvista.com> (raw)
In-Reply-To: <1128089827.3111.2.camel@windu.rchland.ibm.com>
As far as I've heard, there's gonna be a megre quite soon... :)
Anyway, I guess it'd be better if Pavel ntroduced the new patch against
the latest linux-mtd code.
Best regards,
Vitaly
Josh Boyer wrote:
>On Fri, 2005-09-30 at 18:14 +0400, Vitaly Wool wrote:
>
>
>>Hi Pavel,
>>
>>it looks like your patch is not against the latest linux-mtd CVS sources
>>since there's no such things as mtd_pm_dev in the current one. Please
>>correct me if I'm mistaken.
>>
>>
>
>I'm assuming Pavel is just fixing up what's in the mainline kernel.
>This happens quite often, since MTD doesn't sync all too much for
>various reasons.
>
>When a sync is done, stuff like this usually gets picked up in some form
>for the MTD CVS tree. See the commit messages that say things like
>"Merge with upstream".
>
>josh
>
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Wool <vwool@ru.mvista.com>
To: Josh Boyer <jdub@us.ibm.com>
Cc: Pavel Machek <pavel@ucw.cz>,
dwmw2@infradead.org, kernel list <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org
Subject: Re: [patch] switch mtd to new driver model & cleanups
Date: Fri, 30 Sep 2005 22:12:32 +0400 [thread overview]
Message-ID: <433D8010.1090701@ru.mvista.com> (raw)
In-Reply-To: <1128089827.3111.2.camel@windu.rchland.ibm.com>
As far as I've heard, there's gonna be a megre quite soon... :)
Anyway, I guess it'd be better if Pavel ntroduced the new patch against
the latest linux-mtd code.
Best regards,
Vitaly
Josh Boyer wrote:
>On Fri, 2005-09-30 at 18:14 +0400, Vitaly Wool wrote:
>
>
>>Hi Pavel,
>>
>>it looks like your patch is not against the latest linux-mtd CVS sources
>>since there's no such things as mtd_pm_dev in the current one. Please
>>correct me if I'm mistaken.
>>
>>
>
>I'm assuming Pavel is just fixing up what's in the mainline kernel.
>This happens quite often, since MTD doesn't sync all too much for
>various reasons.
>
>When a sync is done, stuff like this usually gets picked up in some form
>for the MTD CVS tree. See the commit messages that say things like
>"Merge with upstream".
>
>josh
>
>
>
>
next prev parent reply other threads:[~2005-09-30 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 12:17 [patch] switch mtd to new driver model & cleanups Pavel Machek
2005-09-30 12:17 ` Pavel Machek
2005-09-30 14:02 ` Russell King
2005-09-30 14:02 ` Russell King
2005-09-30 14:14 ` Vitaly Wool
2005-09-30 14:14 ` Vitaly Wool
2005-09-30 14:17 ` Josh Boyer
2005-09-30 14:17 ` Josh Boyer
2005-09-30 18:12 ` Vitaly Wool [this message]
2005-09-30 18:12 ` Vitaly Wool
2005-09-30 18:18 ` Russell King
2005-09-30 18:18 ` Russell King
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=433D8010.1090701@ru.mvista.com \
--to=vwool@ru.mvista.com \
--cc=dwmw2@infradead.org \
--cc=jdub@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pavel@ucw.cz \
/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.