Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] hostapd: remove gnutls support
Date: Fri, 28 Dec 2012 21:54:30 +0100	[thread overview]
Message-ID: <877go1zym1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1356724043-8879-2-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Fri, 28 Dec 2012 16:47:18 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 Gustavo> hostapd isn't API compatible with gnutls3 so remove support.
 Gustavo> It's probably hardly used since openssl is far more common,
 Gustavo> and hostapd can use its internal routines if it's not
 Gustavo> available.

I've resuffled this to come before the gnutls one and committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-12-28 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 19:47 [Buildroot] [PATCH 1/7] gnutls: bump to version 3.1.5 Gustavo Zacarias
2012-12-28 19:47 ` [Buildroot] [PATCH 2/7] hostapd: remove gnutls support Gustavo Zacarias
2012-12-28 20:54   ` Peter Korsgaard [this message]
2012-12-28 19:47 ` [Buildroot] [PATCH 3/7] wpa_supplicant: " Gustavo Zacarias
2012-12-28 19:47 ` [Buildroot] [PATCH 4/7] ntfs-3g: needs libgcrypt Gustavo Zacarias
2012-12-28 19:47 ` [Buildroot] [PATCH 5/7] glib-networking: fix build failure with gnutls3 Gustavo Zacarias
2012-12-28 19:47 ` [Buildroot] [PATCH 6/7] network-manager: needs libgcrypt Gustavo Zacarias
2012-12-28 19:47 ` [Buildroot] [PATCH 7/7] connman: bump to version 1.10 Gustavo Zacarias
2012-12-28 20:00 ` [Buildroot] [PATCH 1/7] gnutls: bump to version 3.1.5 Thomas Petazzoni
2012-12-28 20:01   ` Gustavo Zacarias
2012-12-28 20:52 ` Peter Korsgaard
2012-12-28 21:27 ` Peter Korsgaard

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=877go1zym1.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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