From: Artem Bityutskiy <dedekind1@gmail.com>
To: Rohit Hassan Sathyanarayan <rohit.hs@samsung.com>
Cc: Vivek Dalal <vivek.dalal@siso.com>,
'David Woodhouse' <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/1][MTD-UTILS] Adding run-time mtd partitioning utility
Date: Mon, 23 Aug 2010 17:37:04 +0300 [thread overview]
Message-ID: <1282574224.24044.73.camel@localhost> (raw)
In-Reply-To: <000001cb2f11$85fb9cc0$91f2d640$%hs@samsung.com>
On Thu, 2010-07-29 at 17:00 +0530, Rohit Hassan Sathyanarayan wrote:
> Hi All
>
> Sending the patch on mtd-utils for run-time partitioning utility.
>
>
>
> Signed-off-by: Rohit HS <rohit.hs@samsung.com>
Not taking this so far. Let's first create proper and mergeble kernel
implementation first, then will add the user-space utility, ok?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-08-23 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 11:30 [PATCH 1/1][MTD-UTILS] Adding run-time mtd partitioning utility Rohit Hassan Sathyanarayan
2010-08-23 14:37 ` Artem Bityutskiy [this message]
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=1282574224.24044.73.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rohit.hs@samsung.com \
--cc=vivek.dalal@siso.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).