Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] BoringSSL library support in buildroot
Date: Sat, 19 Nov 2016 20:41:10 +0100	[thread overview]
Message-ID: <20161119204110.5ba9f1f9@gmx.net> (raw)
In-Reply-To: <CAHBw83dx-Hytbtd8DQmfY1Nziu302K+2ONeLy0R=VNc2w=gPnQ@mail.gmail.com>

Hello Anand,

On Fri, 18 Nov 2016 14:19:30 +0530, Anand Sivaram <aspnair@gmail.com> wrote:

> Thanks Thomas for the clarification :)
> 

Take a look at [1] for boringssl support ;-)

Regards,
Peter

[1] https://patchwork.ozlabs.org/patch/696886/

> Anand
> 
> On 18 November 2016 at 14:17, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
> 
> > Hello,
> >
> > On Fri, 18 Nov 2016 09:02:21 +0530, Anand Sivaram wrote:
> >
> > > Is there any plan for supporting Google's BoringSSL in buildroot?
> > > It is gaining momentum nowadays.
> >
> > The plan in Buildroot is like in most open-source project: merge
> > patches that are proposed/contributed.
> >
> > So if someone proposes a patch to add support for BoringSSL, Buildroot
> > will have support for it. If nobody proposes a patch, then we won't
> > have BoringSSL support.
> >
> > It's as simple as that :)
> >
> > Best regards,
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Free Electrons
> > Embedded Linux and Kernel engineering
> > http://free-electrons.com
> >

  reply	other threads:[~2016-11-19 19:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18  3:32 [Buildroot] BoringSSL library support in buildroot Anand Sivaram
2016-11-18  8:47 ` Thomas Petazzoni
2016-11-18  8:49   ` Anand Sivaram
2016-11-19 19:41     ` Peter Seiderer [this message]
2016-11-20  5:36       ` Anand Sivaram

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=20161119204110.5ba9f1f9@gmx.net \
    --to=ps.report@gmx.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