From: Artem.Bityutskiy@nokia.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clps711x/ceiva: port to use physmap flash
Date: Fri, 03 Jun 2011 08:31:09 +0300 [thread overview]
Message-ID: <1307079069.4405.142.camel@localhost> (raw)
In-Reply-To: <BANLkTimG86aN5hUBy=GgpMAxhiQSPbetPg@mail.gmail.com>
On Fri, 2011-06-03 at 09:17 +0400, Dmitry Eremin-Solenikov wrote:
> On 6/3/11, Artem Bityutskiy <Artem.Bityutskiy@nokia.com> wrote:
> > On Fri, 2011-06-03 at 09:02 +0400, Dmitry Eremin-Solenikov wrote:
> >> On 6/3/11, Artem Bityutskiy <Artem.Bityutskiy@nokia.com> wrote:
> >> > On Thu, 2011-06-02 at 15:54 +0400, Dmitry Eremin-Solenikov wrote:
> >> >> Port ceiva machine to use physmap flash instead of custom mapping
> >> >> driver
> >> >> (which even can't compile cleanly with current kernels). All info
> >> >> is gathered from drivers/mtd/maps/ceiva.c. Compile tested only.
> >> >>
> >> >> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> >> >> ---
> >> >> arch/arm/mach-clps711x/ceiva.c | 60
> >> >> ++++++++++++++++++++++++++++++++++++++++
> >> >> 1 files changed, 60 insertions(+), 0 deletions(-)
> >> >
> >> > Is ceiva used and not dead? May be we could kill it completely?
> >>
> >> No functional changes to board file since start of git history. Also
> >> I don't know how useful can be contemporary Linux on 4 MiB of RAM
> >
> > I also noticed that no one is interested in this board for long time. So
> > I suggest to remove ceiva support altogether via some arm tree.
>
> Anyway the patch removing mtd support can be pushed via mtd tree
> (there is really no point on mtd/maps/ceiva.c), and removing ceiva
> depends on Russell's decision.
If you care about conflicts and how to merge all that - you can remove
ceiva via the arm tree, and at the same time modify the driver in the
mtd tree, and we'll just put a not to the commit message that during the
merge this change has to be discarded. Linus did a similar thing this
merge window for one board which mtd modified and arm tree removed.
--
Best Regards,
Artem Bityutskiy (????? ????????)
next prev parent reply other threads:[~2011-06-03 5:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 11:54 [PATCH 1/2] clps711x/ceiva: port to use physmap flash Dmitry Eremin-Solenikov
2011-06-02 11:54 ` [PATCH 2/2] mtd: drop ceiva map driver Dmitry Eremin-Solenikov
2011-06-03 15:49 ` Artem Bityutskiy
2011-06-04 8:23 ` Dmitry Eremin-Solenikov
2011-06-03 4:38 ` [PATCH 1/2] clps711x/ceiva: port to use physmap flash Artem Bityutskiy
2011-06-03 5:02 ` Dmitry Eremin-Solenikov
2011-06-03 5:10 ` Artem Bityutskiy
2011-06-03 5:17 ` Dmitry Eremin-Solenikov
2011-06-03 5:21 ` Artem Bityutskiy
2011-06-03 5:31 ` Artem Bityutskiy [this message]
2011-06-03 6:07 ` Dmitry Eremin-Solenikov
2011-06-03 7:54 ` Russell King - ARM Linux
2011-06-03 9:21 ` Dmitry Eremin-Solenikov
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=1307079069.4405.142.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=linux-arm-kernel@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 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).