From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Ricard Wanderlof <ricard.wanderlof@axis.com>,
dedekind1@gmail.com,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Tim Bird <tim.bird@am.sony.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC/PATCH 0/1] ubi: Add ubiblock driver
Date: Mon, 3 Dec 2012 23:03:05 +0200 [thread overview]
Message-ID: <20121203230305.7be51ad2.shmulik.ladkani@gmail.com> (raw)
In-Reply-To: <CALF0-+Vab6HZX-yRh0N6HxRSu4GavNXTpzrF6Ry7sDFwAXMHeg@mail.gmail.com>
Hi Ezequiel,
On Mon, 3 Dec 2012 16:33:01 -0300 Ezequiel Garcia <elezegarcia@gmail.com> wrote:
> Hope this helps,
Helps indeed, thanks.
So basically you need ubiblock to state it supports flushing caches, and
properly handle REQ_FLUSH in its request_fn.
Regards,
Shmulik
next prev parent reply other threads:[~2012-12-03 21:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 22:39 [RFC/PATCH 0/1] ubi: Add ubiblock driver Ezequiel Garcia
2012-11-21 5:28 ` Ricard Wanderlof
2012-11-21 9:56 ` Thomas Petazzoni
2012-11-21 10:00 ` Ricard Wanderlof
2012-11-21 10:05 ` Thomas Petazzoni
2012-11-24 21:02 ` Ezequiel Garcia
2012-11-25 7:36 ` Shmulik Ladkani
2012-11-30 11:24 ` Artem Bityutskiy
2012-12-02 17:39 ` Shmulik Ladkani
2012-12-03 0:58 ` Ezequiel Garcia
2012-12-03 19:33 ` Ezequiel Garcia
2012-12-03 21:03 ` Shmulik Ladkani [this message]
2012-11-30 11:18 ` Artem Bityutskiy
2012-11-30 11:15 ` Artem Bityutskiy
2012-11-21 10:00 ` Thomas Petazzoni
2012-11-21 10:42 ` Ezequiel Garcia
2012-11-30 11:25 ` Artem Bityutskiy
2012-11-30 11:08 ` Artem Bityutskiy
2012-11-30 20:43 ` Ezequiel Garcia
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=20121203230305.7be51ad2.shmulik.ladkani@gmail.com \
--to=shmulik.ladkani@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=elezegarcia@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=ricard.wanderlof@axis.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tim.bird@am.sony.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