Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9566] [kmod] Compilation fails with uclibc
Date: Fri, 06 Jan 2017 18:54:30 +0000	[thread overview]
Message-ID: <bug-9566-163-z86vNCVD7B@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9566-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9566

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Peter Korsgaard <jacmet@uclibc.org> ---
The uClibc-ng patch has now been applied:

commit ffad94e6ddde09c8388bdc0b5f825ddf77702182
Author: Waldemar Brodkorb <wbx@openadk.org>
Date:   Wed Dec 28 18:29:01 2016 +0100

    uclibc: add kernel module syscall wrappers

    Revert the decision to remove the wrappers, but remove the extra
    Config symbol and add it by default. Required for kmod package.

    Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-01-06 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  8:27 [Buildroot] [Bug 9566] New: [kmod] Compilation fails with uclibc bugzilla at busybox.net
2017-01-06 18:23 ` [Buildroot] [Bug 9566] " bugzilla at busybox.net
2017-01-06 18:54 ` bugzilla at busybox.net [this message]
2017-07-13 14:08 ` bugzilla at busybox.net
2017-07-23  7:45 ` bugzilla at busybox.net
2018-01-16 23:02 ` bugzilla at busybox.net

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=bug-9566-163-z86vNCVD7B@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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