From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] fs: add pread and pwrite functions
Date: Tue, 19 Feb 2013 21:30:59 +0100 [thread overview]
Message-ID: <20130219202941.GA20171@x61s.8.8.8.8> (raw)
In-Reply-To: <20130219193339.GF25672@pengutronix.de>
Hi Sascha,
On Tue, Feb 19, 2013 at 08:33:39PM +0100, Sascha Hauer wrote:
> Hi Alexander,
>
> On Sun, Feb 17, 2013 at 10:05:01PM +0100, Alexander Aring wrote:
> > Add pread and pwrite functions.
> >
> > Split read and write functions to save some space.
> > The functions pread and pwrite saves and sets the file
> > position to a given offset and restore them afterwards.
> >
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
>
> This currently breaks compilation of the nandtest command. We have two
> options: Either rename pread/pwrite functions in the nandtest command or
> just drop the static versions in the nandtest command.
>
> Sascha
>
Yes, I know... I have already Patches for this. I punish myself, because
it were better to add this changes into this patch series.
First patch series v1 has them include.
I will resend them now.
Regards
Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-02-19 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 21:04 [RFC PATCH v2 0/2] " Alexander Aring
2013-02-17 21:05 ` [PATCH 1/2] fs: fix return type of read Alexander Aring
2013-02-17 21:05 ` [PATCH 2/2] fs: add pread and pwrite functions Alexander Aring
2013-02-18 10:17 ` Sascha Hauer
2013-02-18 15:13 ` Alexander Aring
2013-02-19 19:33 ` Sascha Hauer
2013-02-19 20:30 ` Alexander Aring [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=20130219202941.GA20171@x61s.8.8.8.8 \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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