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 v1 1/3] aufs-standalone: new package
Date: Tue, 1 Dec 2015 23:05:51 +0100	[thread overview]
Message-ID: <20151201230551.7eabb769@free-electrons.com> (raw)
In-Reply-To: <1438387017-10597-1-git-send-email-christian@paral.in>

Christian,

On Fri, 31 Jul 2015 16:56:55 -0700, Christian Stewart wrote:
> aufs-standalone is a metapackage that downloads the correct
> aufs-standalone sources for patching the kernel with the aufs
> filesystem. The package is not selectable because it does nothing but
> download the sources on default. It is a dependency of the Aufs kernel
> extension.
> 
> Signed-off-by: Christian Stewart <christian@paral.in>

Your patches are 4 months old, and you got a lot of review comments.
Could you address them and resend an updated version, if you are still
interested in getting aufs support merged in Buildroot ?

In the mean time, I'll mark your patches as Changes Requested in
patchwork.

Thanks!

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

      parent reply	other threads:[~2015-12-01 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 23:56 [Buildroot] [PATCH v1 1/3] aufs-standalone: new package Christian Stewart
2015-07-31 23:56 ` [Buildroot] [PATCH v1 2/3] aufs: new kernel extension Christian Stewart
2015-08-03 21:13   ` Yann E. MORIN
2015-08-03 21:16     ` Yann E. MORIN
2015-08-03 21:23     ` Christian Stewart
2015-08-03 22:22       ` Floris Bos
2015-07-31 23:56 ` [Buildroot] [PATCH v1 3/3] aufs-util: new package Christian Stewart
2015-08-03 20:41 ` [Buildroot] [PATCH v1 1/3] aufs-standalone: " Yann E. MORIN
2015-08-03 20:59   ` Christian Stewart
2015-12-01 22:05 ` 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=20151201230551.7eabb769@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