mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] devfs: be more lax with partition boundaries
Date: Thu, 7 May 2015 10:57:02 +0200	[thread overview]
Message-ID: <20150507085702.GR6325@pengutronix.de> (raw)
In-Reply-To: <1430988346-25450-1-git-send-email-u.kleine-koenig@pengutronix.de>

On Thu, May 07, 2015 at 10:45:45AM +0200, Uwe Kleine-König wrote:
> If a partition starts inside its parent device but is too big such that
> it extends over the device boundary, just chop it to the device's end.
> 
> This matches the behaviour of Linux.
> 
> The motivation for this change is that it makes it possible in some
> cases to have the partitioning in a device tree fixed and still allow
> different flash sizes.

When doing it someone is probably annoyed about the warning pretty soon.
I know we just talked whether I would accept this patch, but now I
realized that the correct way to extend the last partition to the end of
the device is to use size 0. This works under barebox and Linux.

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

  reply	other threads:[~2015-05-07  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  8:45 Uwe Kleine-König
2015-05-07  8:57 ` Sascha Hauer [this message]
2015-05-07  9:09   ` Uwe Kleine-König

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=20150507085702.GR6325@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=u.kleine-koenig@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