mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: iproute2 & other software
Date: Wed, 2 Mar 2016 12:37:12 -0800	[thread overview]
Message-ID: <0DED8CA5-AABF-471F-AF89-26BFCB3F7B40@gmail.com> (raw)
In-Reply-To: <CAOp4FwSd4bwCadzLnd-0o+v4VBouhH47JMN___xWKQH9O82nyA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]


> On Mar 2, 2016, at 11:19 AM, Loganaden Velvindron <loganaden@gmail.com> wrote:
> 
> Hi All,
> 
> Stephen (iproute2) sent me a mail telling me that he rejected my patch to iproute2 for musl support:
> 
> 1st reply:
> "
> I was waiting for others who had more to say on this.
> Ok with providing small fixes, but can't really guarantee iproute to
> work with other libraries.
> "
> 
> & 2nd is :
> "
> Sorry, I have to reject this.
> All include files in include/linux come from headers automatically generated from upstream
> Linux source. This is the only way to ensure long term ABI/API consistency
> with kernel.
> 
> Either fix musl or submit patches to upstream kernel and get them merged.
> “

Where is your patch.

> 
> Can we look into providing somekind of compatibility layer for header files so that it's easier to get upstream projects like iproute2 to support musl ?
> 
> Kind regards,
> //Logan
> C-x-C-c
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

  reply	other threads:[~2016-03-02 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 19:19 Loganaden Velvindron
2016-03-02 20:37 ` Khem Raj [this message]
2016-03-02 20:39   ` Loganaden Velvindron
2016-03-02 20:44     ` Khem Raj
2016-03-02 23:18       ` Rich Felker
2016-03-02 20:49 ` Szabolcs Nagy
2016-03-02 23:30   ` Rich Felker
2016-03-03 10:10     ` Szabolcs Nagy
2016-03-03 16:00       ` Rich Felker
2016-03-03 16:12 Kylie McClain
2016-03-03 17:01 ` Szabolcs Nagy
2016-03-03 19:05   ` Rich Felker

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=0DED8CA5-AABF-471F-AF89-26BFCB3F7B40@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).