From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1grHmI-00071z-Qr for barebox@lists.infradead.org; Wed, 06 Feb 2019 07:37:52 +0000 Received: by mail-wm1-x342.google.com with SMTP id p6so1493795wmc.1 for ; Tue, 05 Feb 2019 23:37:50 -0800 (PST) MIME-Version: 1.0 References: <20190204144641.19600-1-s.hauer@pengutronix.de> <20190206073324.3r3zuogav6bqnkzr@pengutronix.de> In-Reply-To: <20190206073324.3r3zuogav6bqnkzr@pengutronix.de> From: Andrey Smirnov Date: Tue, 5 Feb 2019 23:37:37 -0800 Message-ID: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH 0/5] 32-bit lseek and /dev/mem fixes/improvements To: Sascha Hauer Cc: Barebox List On Tue, Feb 5, 2019 at 11:33 PM Sascha Hauer wrote: > > On Tue, Feb 05, 2019 at 01:44:31PM -0800, Andrey Smirnov wrote: > > On Mon, Feb 4, 2019 at 6:46 AM Sascha Hauer 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()" > > I applied these two now (although squashed into a single commit)... > > > > > appear to be missing and, as a result: > > > > "fs: Avoid division in mem_copy()" > > ...and rewrote this commit message. > > > > > 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? > > I thought they wouldn't apply anymore, but I was mistaken. Indeed they > do apply. OK, cool, good to hear they are back! Thanks, Andrey Smirnov _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox