linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Demi Marie Obenour <demiobenour@gmail.com>,
	Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] crypto: qce - Remove driver
Date: Tue, 28 Jul 2026 08:30:45 -0700	[thread overview]
Message-ID: <20260728153045.GB4281@quark> (raw)
In-Reply-To: <CAMRc=Me_uO0oMqjyuZzs7AxjWoSyy-=rT1eshmFQcNH_3H2ygw@mail.gmail.com>

On Mon, Jul 27, 2026 at 06:26:56AM -0700, Bartosz Golaszewski wrote:
> Is disabling it in defconfig an acceptable compromise?

No, that completely misses the point.  The defconfig doesn't matter all
that much.

- Eric

  reply	other threads:[~2026-07-28 15:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  5:06 [PATCH] crypto: qce - Remove driver Eric Biggers
2026-07-24  5:28 ` Greg Kroah-Hartman
2026-07-24  7:36   ` Bartosz Golaszewski
2026-07-24  8:41     ` Greg Kroah-Hartman
2026-07-24  9:29       ` Bartosz Golaszewski
2026-07-24 14:14         ` Eric Biggers
2026-07-24 14:47           ` Bartosz Golaszewski
2026-07-24 15:04             ` Greg Kroah-Hartman
2026-07-24 15:09               ` Eric Biggers
2026-07-24 15:25                 ` Greg Kroah-Hartman
2026-07-24 15:51                   ` Eric Biggers
2026-07-27 13:26                     ` Bartosz Golaszewski
2026-07-28 15:30                       ` Eric Biggers [this message]
2026-07-28 15:22                     ` Eric Biggers
2026-07-24  9:56 ` Sumit Garg
2026-07-24 13:51   ` Eric Biggers

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=20260728153045.GB4281@quark \
    --to=ebiggers@kernel.org \
    --cc=brgl@kernel.org \
    --cc=demiobenour@gmail.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuldeep.singh@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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).