Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] beaglebone: increase size of ext4 more then 60MB
Date: Sat, 8 Apr 2017 15:31:19 +0200	[thread overview]
Message-ID: <20170408153119.6747dc5b@free-electrons.com> (raw)
In-Reply-To: <20170407100323.6871-2-michael@amarulasolutions.com>

Hello,

On Fri,  7 Apr 2017 12:03:23 +0200, Michael Trimarchi wrote:
> This is due to the fact that we removed auto-calculation of the ext4
> filesystem size in
> https://git.buildroot.org/buildroot/commit/?id=c6bca8cef0310bc649240b451989457ce94a8358,
> and we default to 60 MB for the filesystem size, which is not enough
> for this demo
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Tested-by: Michael Trimarchi <michael@amarulasolutions.com>

This shouldn't have my Signed-off-by, but yours, it's your patch, and
you're submitting it. If you really want to credit me, you can always do
something like:

Suggested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Could you resubmit after using your Signed-off-by? Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-04-08 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 10:03 [Buildroot] [PATCH 1/2] uboot: qstrip BR2_TARGET_UBOOT_CUSTOM_DTS_PATH Michael Trimarchi
2017-04-07 10:03 ` [Buildroot] [PATCH 2/2] beaglebone: increase size of ext4 more then 60MB Michael Trimarchi
2017-04-08 13:31   ` Thomas Petazzoni [this message]
2017-04-07 19:46 ` [Buildroot] [PATCH 1/2] uboot: qstrip BR2_TARGET_UBOOT_CUSTOM_DTS_PATH Peter Seiderer
2017-04-08 13:30 ` Thomas Petazzoni

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=20170408153119.6747dc5b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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