From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] aiccu: musl patches
Date: Wed, 25 Mar 2015 23:26:17 +0200 [thread overview]
Message-ID: <20150325212617.GA24658@vostro> (raw)
In-Reply-To: <20150325200955.6a0e54c7@free-electrons.com>
Wed, Mar 25, 2015 at 08:09:55PM +0100, Thomas Petazzoni wrote:
> > package/aiccu/0004-if-ether-header.patch | 23 +++++++++++++++++++++++
> > package/aiccu/0005-res-ninit.patch | 22 ++++++++++++++++++++++
>
> Thanks. What is the upstreaming plan for those patches?
None I'd say, their last release is 8 years old and patches 0001-0003
have been around for quite some time as well.
By the way, please disregard this patch. I just realized 0001 does
exactly the same thing for uclibc that I did with 0005 for musl.
It's better to merge them.
prev parent reply other threads:[~2015-03-25 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:30 [Buildroot] [PATCH] aiccu: musl patches Alex Suykov
2015-03-25 19:09 ` Thomas Petazzoni
2015-03-25 21:26 ` Alex Suykov [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=20150325212617.GA24658@vostro \
--to=alex.suykov@gmail.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