All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] openssl: disable default cryptodev
Date: Thu, 27 Jul 2017 09:13:35 +0100	[thread overview]
Message-ID: <1501143215.22282.145.camel@linuxfoundation.org> (raw)
In-Reply-To: <1501132627-4360-1-git-send-email-huangqy.fnst@cn.fujitsu.com>

On Thu, 2017-07-27 at 13:17 +0800, Huang Qiyu wrote:
> Because according to the other Distros,cryptodev is not enabled.
> If users want enable cryptodev, just have to add "cryptodev-linux"
> into PACKAGECONFIG.

We really need more of a justification for this change. We presumably
enable this for a reason and people probably use it. Why is disabling
it by default a better thing for the project to do? Are there specific
reasons other distros don't enable this?

Cheers,

Richard


      parent reply	other threads:[~2017-07-27  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  5:17 [PATCH v2] openssl: disable default cryptodev Huang Qiyu
2017-07-27  5:31 ` ✗ patchtest: failure for " Patchwork
2017-07-27  8:13 ` Richard Purdie [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=1501143215.22282.145.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=huangqy.fnst@cn.fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.