From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Grigory Milev <G.Milev@sam-solutions.com>,
barebox@lists.infradead.org,
Dmitry Lavnikevich <D.Lavnikevich@sam-solutions.com>,
Dmitry Lavnikevich <d.lavnikevich@sam-solutions.net>
Subject: Re: [PATCH 1/5] mtd: Update internal API to support 64-bit device size
Date: Wed, 12 Mar 2014 21:28:15 +0100 [thread overview]
Message-ID: <20140312202814.GK17250@pengutronix.de> (raw)
In-Reply-To: <20140311075043.GA4321@omega>
On Tue, Mar 11, 2014 at 08:50:44AM +0100, Alexander Aring wrote:
> On Tue, Mar 11, 2014 at 06:29:22AM +0100, Sascha Hauer wrote:
> > > offset but we should do it right at first time.
> >
> > Yes, right. We should make this uint64_t.
> >
>
> There are also more things which needs a uint64_t like the offset
> parameter of libmtd_* functions. :-/
The libmtd functions should be 64bit already. The remaining bits are in
Dmitrys series.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-03-12 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 11:14 Dmitry Lavnikevich
2014-03-10 7:20 ` Sascha Hauer
2014-03-10 8:02 ` Alexander Aring
2014-03-11 5:29 ` Sascha Hauer
2014-03-11 7:50 ` Alexander Aring
2014-03-12 20:28 ` Sascha Hauer [this message]
2014-03-10 11:37 ` Dmitry Lavnikevich
2014-03-10 11:39 Dmitry Lavnikevich
2014-03-12 20:28 ` Sascha Hauer
2014-03-12 20:51 ` Alexander Aring
2014-03-12 20:53 ` Sascha Hauer
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=20140312202814.GK17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=D.Lavnikevich@sam-solutions.com \
--cc=G.Milev@sam-solutions.com \
--cc=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=d.lavnikevich@sam-solutions.net \
/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