From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH v3 0/7] prepare new nanddump options, defaults
Date: Fri, 24 Jun 2011 23:11:12 +0300 [thread overview]
Message-ID: <1308946279.13493.29.camel@koala> (raw)
In-Reply-To: <BANLkTi=b9tnk5tS9FZZ5WP4Nz9PUhMb02A@mail.gmail.com>
On Fri, 2011-06-24 at 10:37 -0700, Brian Norris wrote:
> Are the "ubi-utils" and "tests" meant to have the option of compiling
> separately from the other mtd-utils?
Probably not.
> Are these tools ever distributed separately? If not, do they need to
> be independently buildable?
I do not think that we need ubi-utils to be buildable separately.
> It looks to me like ubi-utils is dependent
> on first compiling "lib", but otherwise, they can all be built
> separately... Anyway, I think this kinda screws with the centralized
> VERSION thing above.
> Why is mtdinfo under ubi-utils? Perhaps it should be moved when it
> replaces flash_info? I think this is a fair interpretation of Item 3
> in the feature-removal plan...
Yeah, it can be moved.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2011-06-24 20:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 15:46 [PATCH v2 0/7] new nanddump defaults Brian Norris
2011-06-21 15:46 ` [PATCH v2 1/7] nanddump: add --bb=METHOD option Brian Norris
2011-06-21 15:46 ` [PATCH v2 2/7] nanddump: remove --skipbad, leaving --bb=skipbad Brian Norris
2011-06-21 15:46 ` [PATCH v2 3/7] nanddump: deprecation messages for old BB options Brian Norris
2011-06-21 19:38 ` Mike Frysinger
2011-06-21 15:46 ` [PATCH v2 4/7] nanddump: warn about new default BB handling Brian Norris
2011-06-21 19:37 ` Mike Frysinger
2011-06-21 15:46 ` [PATCH v2 5/7] feature-removal-schedule: describe nanddump changes Brian Norris
2011-06-21 15:46 ` [PATCH v2 6/7] nanddump: add --oob option Brian Norris
2011-06-21 15:46 ` [PATCH v2 7/7] nanddump: document, warn about future default --omitoob Brian Norris
2011-06-21 19:39 ` Mike Frysinger
2011-06-21 19:40 ` [PATCH v2 0/7] new nanddump defaults Mike Frysinger
2011-06-21 22:36 ` Brian Norris
2011-06-22 16:49 ` [PATCH v3 0/7] prepare new nanddump options, defaults Brian Norris
2011-06-23 15:02 ` Artem Bityutskiy
2011-06-23 15:04 ` Artem Bityutskiy
2011-06-23 15:52 ` Mike Frysinger
2011-06-23 23:00 ` Brian Norris
2011-06-23 23:14 ` Mike Frysinger
2011-06-23 23:27 ` Brian Norris
2011-06-23 23:36 ` Mike Frysinger
2011-06-23 23:40 ` Brian Norris
2011-06-23 23:45 ` Mike Frysinger
2011-06-23 23:48 ` Brian Norris
2011-06-24 20:20 ` Artem Bityutskiy
2011-06-26 7:15 ` Peter Korsgaard
2011-06-24 17:37 ` Brian Norris
2011-06-24 18:28 ` Mike Frysinger
2011-06-24 19:21 ` Artem Bityutskiy
2011-06-24 20:11 ` Artem Bityutskiy [this message]
2011-06-24 20:15 ` Artem Bityutskiy
2011-06-24 19:38 ` Artem Bityutskiy
2011-06-22 16:49 ` [PATCH v3 1/7] nanddump: add --bb=METHOD option Brian Norris
2011-06-22 16:49 ` [PATCH v3 2/7] nanddump: remove --skipbad, leaving --bb=skipbad Brian Norris
2011-06-22 16:49 ` [PATCH v3 3/7] nanddump: update help message for BB method changes Brian Norris
2011-06-22 16:49 ` [PATCH v3 4/7] nanddump: warn about new default BB handling Brian Norris
2011-06-22 16:49 ` [PATCH v3 5/7] feature-removal-schedule: describe nanddump changes Brian Norris
2011-06-22 16:49 ` [PATCH v3 6/7] nanddump: add --oob option Brian Norris
2011-06-22 16:49 ` [PATCH v3 7/7] nanddump: document, warn about future default --omitoob Brian Norris
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=1308946279.13493.29.camel@koala \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.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