mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/5] 32-bit lseek and /dev/mem fixes/improvements
Date: Tue, 5 Feb 2019 13:44:31 -0800	[thread overview]
Message-ID: <CAHQ1cqG1i_AcMBymMLMekokRd6HozomtZYDVznruixs0Z1XVxA@mail.gmail.com> (raw)
In-Reply-To: <20190204144641.19600-1-s.hauer@pengutronix.de>

On Mon, Feb 4, 2019 at 6:46 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> This series ontop of Andreys series (minus the patches that I have
> reverted) makes /dev/mem work for the whole 64bit address space without
> hopefully special casing too much. "fs: set errno in ftruncate()" and
> "fs: devfs: forbid truncation when cdev has no truncate operation" are
> not directly related, I stumbled upon these while working on the
> patches.
>
> See the full series in -next. Comments welcome, if somethings wrong with
> it we can still change.
>

Not sure why, but the following patches:

"fs: Report actual data processed by mem_copy()"
"fs: Share code between mem_write()/mem_read()"

appear to be missing and, as a result:

"fs: Avoid division in mem_copy()"

doesn't actually have mem_copy() function in it. Did the two patches
above just slipped through the cracks or was there a particular reason
you dropped them?

Thanks,
Andrey Smirnov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2019-02-05 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 14:46 Sascha Hauer
2019-02-04 14:46 ` [PATCH 1/5] fs: let truncate take a loff_t argument Sascha Hauer
2019-02-04 14:46 ` [PATCH 2/5] fs: set errno in ftruncate() Sascha Hauer
2019-02-04 14:46 ` [PATCH 3/5] fs: do not call truncate for FILE_SIZE_STREAM sized files Sascha Hauer
2019-02-04 14:46 ` [PATCH 4/5] fs: devfs: forbid truncation when cdev has no truncate operation Sascha Hauer
2019-02-04 14:46 ` [PATCH 5/5] misc: fix /dev/mem size Sascha Hauer
2019-02-05 21:44 ` Andrey Smirnov [this message]
2019-02-06  7:33   ` [PATCH 0/5] 32-bit lseek and /dev/mem fixes/improvements Sascha Hauer
2019-02-06  7:37     ` Andrey Smirnov

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=CAHQ1cqG1i_AcMBymMLMekokRd6HozomtZYDVznruixs0Z1XVxA@mail.gmail.com \
    --to=andrew.smirnov@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