All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhangjian (Bamvor) <bamvor.zhangjian@huawei.com>
To: buildroot@busybox.net
Subject: [Buildroot] Proposal to remove patches from patchwork, or find adopters
Date: Fri, 8 May 2015 09:20:54 +0800	[thread overview]
Message-ID: <554C0F76.3030306@huawei.com> (raw)
In-Reply-To: <20150506235353.7740a9d3@free-electrons.com>

Hi, Thomas

On 2015/5/7 5:53, Thomas Petazzoni wrote:
> Hello,
>
> On April 21th, I sent a personal reminder to all the patch authors who
> had patches older than 15 days pending in Buildroot's patchwork.
...
>   * [RFC,v2,1/5] aarch64: add big endian(aarch64_be) support
>   * [RFC,v2,2/5] aarch64: ilp32: handle special file name
>   * [RFC,v2,3/5] aarch64: ilp32: add ilp32 compiler and linker flags
>   * [RFC,v2,4/5] aarch64: ilp32: add ilp32 build config
>   * [RFC,v2,5/5] aarch64: ilp32 defconfig examples
I will send the next version of these patches in next few days.

thanks

bamvor

>   * [1/1] busybox: add conditional dependency on libselinux (v2)
>
> Thanks,
>
> Thomas Petazzoni
>

  parent reply	other threads:[~2015-05-08  1:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 21:53 [Buildroot] Proposal to remove patches from patchwork, or find adopters Thomas Petazzoni
2015-05-06 22:10 ` Alexey Brodkin
2015-05-06 22:52 ` Emeric Vigier
2015-05-06 23:59 ` Jeremy Kerr
2015-05-07  3:42 ` Baruch Siach
2015-05-07  5:48 ` Bernd Kuhls
2015-05-07  6:54 ` jordi montagne
2015-05-11 14:25   ` jean burgat
2015-05-07  8:13 ` Jérôme Pouiller
2015-05-07  8:21 ` Nathaniel Roach
2015-05-07  9:34 ` Károly Kasza
2015-05-07  9:45 ` Will Wagner
2015-05-07 10:19 ` Samuel Martin
2015-05-07 10:30   ` Thomas Petazzoni
2015-05-07 11:14 ` Carlos Santos
2015-05-15 18:28   ` Carlos Santos
2015-05-15 20:14     ` Carlos Santos
2015-05-16  8:37       ` Thomas Petazzoni
2015-05-08  1:20 ` Zhangjian [this message]
2015-05-08 13:42 ` Maxime Hadjinlian
2015-05-10 10:00 ` Thomas De Schampheleire
2015-05-29 15:08   ` Thomas De Schampheleire
2015-05-11 15:11 ` Steve Calfee

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=554C0F76.3030306@huawei.com \
    --to=bamvor.zhangjian@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.