From: Artem Bityutskiy <dedekind1@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Vitaly Wool <vwool@ru.mvista.com>
Subject: Re: linux-next: Tree for June 24 (mtd + of)
Date: Sun, 26 Jun 2011 12:43:41 +0300 [thread overview]
Message-ID: <1309081426.6618.0.camel@koala> (raw)
In-Reply-To: <BANLkTi=Q-7bCHaH+-z6gnbwvexpGLYH6pA@mail.gmail.com>
On Sun, 2011-06-26 at 00:11 -0600, Grant Likely wrote:
> > 3.0-rc4 does not have this build error when I use the .config file with it...
> > however, I think that 3.0-rc4 also does not build ofpart.ko as it should.
> >
> > Looks to me like changes in drivers/mtd/{Kconfig && Makefile} caused this
> > build error.
>
> The following commit in linux-next appears to be the culprit:
>
> commit 1a6bc893044b961caae1c5a9c6c2065e608da427
> Author: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> Date: Sun May 29 21:32:33 2011 +0400
>
> mtd: prepare to convert of_mtd_parse_partitions to partition parser
>
> Prepare to convert of_mtd_parse_partitions() to usual partitions parser:
> 1) Register ofpart parser
> 2) Internally don't use passed device for error printing
> 3) Add device_node to mtd_part_parser_data struct
> 4) Move of_mtd_parse_partitions from __devinit to common text section
> 5) add ofpart to the default list of partition parsers
>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
>
> It adds a module_init() call to ofpart.c which does not work the way
> that ofpart.c is linked to mtdcore.o. Seems like that commit series
> still needs work.
OK, let's ask Dmitry to take a look at this.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2011-06-26 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 5:58 linux-next: Tree for June 24 Stephen Rothwell
2011-06-24 16:04 ` linux-next: Tree for June 24 (mtd + of) Randy Dunlap
2011-06-24 20:26 ` Artem Bityutskiy
2011-06-24 20:38 ` Randy Dunlap
2011-06-25 6:35 ` Artem Bityutskiy
2011-06-25 22:20 ` Randy Dunlap
2011-06-26 6:11 ` Grant Likely
2011-06-26 9:43 ` Artem Bityutskiy [this message]
2011-06-26 20:09 ` Dmitry Eremin-Solenikov
[not found] ` <20110624155822.cb8cf6eb.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-06-24 16:28 ` [PATCH] staging: fix more iio builds when IIO_RING_BUFFER is not enabled Randy Dunlap
[not found] ` <20110624092832.36ef2eae.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-06-25 11:16 ` Jonathan Cameron
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=1309081426.6618.0.camel@koala \
--to=dedekind1@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=vwool@ru.mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).