public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: dhowells@redhat.com, linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: Bug in physmap driver?
Date: Thu, 16 Apr 2009 16:09:41 +0100	[thread overview]
Message-ID: <11416.1239894581@redhat.com> (raw)
In-Reply-To: <20090416150630.GR1760@mail.wantstofly.org>

Lennert Buytenhek <buytenh@wantstofly.org> wrote:

> That would suggest that dev->resource[i].end is off-by-one?

Actually, that's a good question: should end be one after the last useful
addres, or should it be that last useful address?

David

  reply	other threads:[~2009-04-16 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 15:00 Bug in physmap driver? David Howells
2009-04-16 15:06 ` Lennert Buytenhek
2009-04-16 15:09   ` David Howells [this message]
2009-04-16 15:14     ` Lennert Buytenhek
2009-04-16 15:27       ` David Howells
2009-04-16 16:23         ` Nicolas Pitre

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=11416.1239894581@redhat.com \
    --to=dhowells@redhat.com \
    --cc=buytenh@wantstofly.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    /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