public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/3] Export UBI map/unmap/is_mapped in userspace v2
Date: Tue, 20 Jan 2009 18:34:11 +0100	[thread overview]
Message-ID: <71cd59b00901200934t141db76axcec187f20f35d4cf@mail.gmail.com> (raw)
In-Reply-To: <1232361760.22350.25.camel@localhost.localdomain>

Ok, thanks for your comments.
We'll do that and send the result next week.

On Mon, Jan 19, 2009 at 11:42 AM, Artem Bityutskiy
<dedekind@infradead.org> wrote:
> On Mon, 2009-01-19 at 12:09 +0200, Artem Bityutskiy wrote:
>> Hi,
>>
>> Some obvious things are commented below.
>>
>
> Err, and also do not forget to zap the CONFIG_MTD_UBI_DEBUG_USERSPACE_IO
> from UBI Kconfig.
>
> --
> Best regards,
> Artem Bityutskiy (Битюцкий Артём)
>
>



-- 
Corentin Chary
http://xf.iksaif.net

      reply	other threads:[~2009-01-20 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  9:22 [PATCH 0/3] Export UBI map/unmap/is_mapped in userspace v2 Corentin Chary
2009-01-07  9:25 ` [PATCH 1/3] UBI: map operation via ioctl Corentin Chary
2009-01-07  9:27 ` [PATCH 2/3] UBI: unmap " Corentin Chary
2009-01-07  9:29 ` [PATCH 3/3] UBI: is_mapped " Corentin Chary
2009-01-07  9:32 ` [PATCH 0/3] Export UBI map/unmap/is_mapped in userspace v2 Artem Bityutskiy
2009-01-07  9:40   ` Corentin Chary
2009-01-07 12:15 ` Artem Bityutskiy
2009-01-07 13:40   ` Corentin Chary
2009-01-18 14:47 ` Artem Bityutskiy
2009-01-18 17:24   ` Corentin Chary
2009-01-19  9:38     ` Corentin Chary
2009-01-19 10:09       ` Artem Bityutskiy
2009-01-19 10:42         ` Artem Bityutskiy
2009-01-20 17:34           ` Corentin Chary [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=71cd59b00901200934t141db76axcec187f20f35d4cf@mail.gmail.com \
    --to=corentin.chary@gmail.com \
    --cc=dedekind@infradead.org \
    --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