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 00/14] fs: cleanups and enhancements
Date: Fri, 1 Dec 2017 17:33:42 +0100	[thread overview]
Message-ID: <20171201173342.40eacec2@windsurf.lan> (raw)
In-Reply-To: <cover.1510508733.git.yann.morin.1998@free.fr>

Hello,

On Sun, 12 Nov 2017 18:45:47 +0100, Yann E. MORIN wrote:

> Yann E. MORIN (14):
>       core: sort packages and eliminate duplicates in show-targets
>       linux: split overly-long dependency line for readability
>       linux: meddle not in the internals of filesystems
>       fs/initramfs: cleanups, enhance comments
>       fs/ext2: use a post-gen hook rather than a post-target rule
>       fs/cpio: use a post-gen hook rather than a post-target rule
>       fs/common: get rid of post-target rules
>       fs: remove TARGET_DIR_WARNING_FILE late
>       fs: don't pollute $(BUILD_DIR) with temp files
>       fs/iso9660: don't pollute $(BUILD_DIR) with temp dir
>       fs: don't remove intermediate files

I have applied the patch series up to this point to the next branch.
Besides minor typo fixes here and there, I didn't change anything.

>       fs: move actions common to all filesystems to their own rule
>       core: finalise target in its own location

I will continue to apply the remainder of this series soon. I need it
for the TLP work :-)

Thanks!

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

      parent reply	other threads:[~2017-12-01 16:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 17:45 [Buildroot] [PATCH 00/14] fs: cleanups and enhancements Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 01/14] core: sort packages and eliminate duplicates in show-targets Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 02/14] linux: split overly-long dependency line for readability Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 03/14] linux: meddle not in the internals of filesystems Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 04/14] fs/initramfs: cleanups, enhance comments Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 05/14] fs/ext2: use a post-gen hook rather than a post-target rule Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 06/14] fs/cpio: " Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 07/14] fs/common: get rid of post-target rules Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 08/14] fs: remove TARGET_DIR_WARNING_FILE late Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 09/14] fs: don't pollute $(BUILD_DIR) with temp files Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 10/14] fs/iso9660: don't pollute $(BUILD_DIR) with temp dir Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 11/14] fs: don't remove intermediate files Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 12/14] fs: move actions common to all filesystems to their own rule Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 13/14] core: finalise target in its own location Yann E. MORIN
2017-11-12 17:45 ` [Buildroot] [PATCH 14/14] TEST-ME Yann E. MORIN
2017-11-12 17:53   ` Yann E. MORIN
2017-12-01 16:33 ` Thomas Petazzoni [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=20171201173342.40eacec2@windsurf.lan \
    --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