From: Richard Weinberger <richard@nod.at>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: tglx@linutronix.de, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] UBI: Kill data type hint
Date: Sun, 13 May 2012 16:37:09 +0200 [thread overview]
Message-ID: <4FAFC715.50405@nod.at> (raw)
In-Reply-To: <1336919166.2003.7.camel@koala>
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
Artem,
Am 13.05.2012 16:26, schrieb Artem Bityutskiy:
> I'd like to merge it to 3.5, so making it easier to review would be
> great. Could you please do split it at least on 2 patches, may be even
> thee:
Will do!
Expect the patch set tomorrow plus v3 of UBI fastmap.
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2012-05-13 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 12:14 [RFC] UBI: Kill data type hint Richard Weinberger
2012-05-11 12:14 ` [PATCH] " Richard Weinberger
2012-05-13 14:41 ` Artem Bityutskiy
2012-05-13 15:28 ` Richard Weinberger
2012-05-13 14:26 ` Artem Bityutskiy
2012-05-13 14:37 ` Richard Weinberger [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=4FAFC715.50405@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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).