From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/9] ext2: add help text for BR2_TARGET_ROOTFS_EXT2_BLOCKS
Date: Thu, 4 May 2017 17:15:24 +0200 [thread overview]
Message-ID: <20170504171524.10882d10@free-electrons.com> (raw)
In-Reply-To: <78e1595a645865a4e5862b84abf8a66173f2ccf6.1493654310.git.yann.morin.1998@free.fr>
Hello,
On Mon, 1 May 2017 17:58:36 +0200, Yann E. MORIN wrote:
> From: J Evans <g4@novadsp.com>
>
> Signed-off-by: J Evans <g4@novadsp.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> fs/ext2/Config.in | 2 ++
> 1 file changed, 2 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-04 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 15:58 [Buildroot] [PATCH 0/9] fs/ext2: cleanups and improvements Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 1/9] ext2: add help text for BR2_TARGET_ROOTFS_EXT2_BLOCKS Yann E. MORIN
2017-05-04 15:15 ` Thomas Petazzoni [this message]
2017-05-01 15:58 ` [Buildroot] [PATCH 2/9] package/mke2img: check nb_blocks is specified Yann E. MORIN
2017-05-13 13:17 ` Thomas Petazzoni
2017-05-01 15:58 ` [Buildroot] [PATCH 3/9] package/mke2img: specifying zero inodes means auto Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 4/9] fs/ext2: always pass the number of inodes Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 5/9] fs/ext2: always pass the label option Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 6/9] fs/ext2: allow reserving zero block for root Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 7/9] fs/ext2: simplify code Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 8/9] package/mke2img: add option to specify block size Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 9/9] fs/ext2: " Yann E. MORIN
2017-05-01 19:18 ` [Buildroot] [PATCH 0/9] fs/ext2: cleanups and improvements Thomas Petazzoni
2017-05-01 20:58 ` Yann E. MORIN
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=20170504171524.10882d10@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