From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] libubi: make `ubi_dev_present()' a library function
Date: Fri, 27 Jan 2012 16:51:38 +0200 [thread overview]
Message-ID: <1327675898.29385.5.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1327563110-23966-1-git-send-email-computersforpeace@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
On Wed, 2012-01-25 at 23:31 -0800, Brian Norris wrote:
> We will use this function in ubinfo.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Many thanks Brian for the fixes, pushed to mtd-utils.git!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-27 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 7:31 [PATCH 1/2] libubi: make `ubi_dev_present()' a library function Brian Norris
2012-01-26 7:31 ` [PATCH 2/2] ubinfo: fix `--all' for non-consecutive device numbers Brian Norris
2012-01-26 8:53 ` Brian Foster
2012-01-27 18:28 ` Brian Norris
2012-01-30 8:32 ` Brian Foster
2012-01-27 14:51 ` 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=1327675898.29385.5.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@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