From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] devfs: be more lax with partition boundaries
Date: Thu, 7 May 2015 11:09:17 +0200 [thread overview]
Message-ID: <20150507090917.GJ12306@pengutronix.de> (raw)
In-Reply-To: <20150507085702.GR6325@pengutronix.de>
Hello Sascha,
On Thu, May 07, 2015 at 10:57:02AM +0200, Sascha Hauer wrote:
> 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
well, we talked about a change in barebox that makes it match the
behaviour of Linux. So critic to the actual implementation is fine.
> 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.
Great. Just tested this and it works fine. (I don't know if Linux really
handles this this way, but barebox does and gives the right explicit
size to Linux.)
\o/
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-05-07 9:09 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
2015-05-07 9:09 ` Uwe Kleine-König [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=20150507090917.GJ12306@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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