From: Julian Braha <julianbraha@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Zhu Yanjun <zyjzyj2000@gmail.com>,
Doug Ledford <dledford@redhat.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: infiniband: sw: rxe: fix kconfig dependency on CRYPTO
Date: Tue, 23 Feb 2021 16:54:37 -0500 [thread overview]
Message-ID: <10464303.FBcTZR2von@ubuntu-mate-laptop> (raw)
In-Reply-To: <CAK8P3a1jRS=QyTxJzSxfEsaAuF5HnOXbv4MOu8b5EZWEhUep=Q@mail.gmail.com>
On Tuesday, February 23, 2021 4:26:44 PM EST Arnd Bergmann wrote:
> On Tue, Feb 23, 2021 at 9:46 PM Julian Braha <julianbraha@gmail.com> wrote:
> >
> > I have other similar patches that I intend to submit. What should I do,
> > going forward? Should I use "depends on CRYPTO" for cases like these?
> > Should I resubmit this patch with that change?
>
> No, we should not mix the two methods, that just leads to circular dependencies.
>
> How many more patches do you have that need to get merged?
>
> If it's only a few, I'd suggest merging them first before we consider a
> broader change. If the problem is very common, we may want to
> think about alternative approaches first, and then change everything
> at once.
>
> Arnd
>
Sorry, I don't have a specific number, but it's certainly under a dozen patches.
next prev parent reply other threads:[~2021-02-23 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 23:32 [PATCH] drivers: infiniband: sw: rxe: fix kconfig dependency on CRYPTO Julian Braha
2021-02-21 6:48 ` Leon Romanovsky
2021-02-22 2:39 ` Zhu Yanjun
2021-02-22 13:00 ` Leon Romanovsky
2021-02-22 15:58 ` Jason Gunthorpe
2021-02-22 16:26 ` Randy Dunlap
2021-02-22 16:46 ` Jason Gunthorpe
2021-02-22 16:50 ` Leon Romanovsky
2021-02-22 16:53 ` Randy Dunlap
2021-02-23 20:36 ` Arnd Bergmann
2021-02-23 20:40 ` Arnd Bergmann
[not found] ` <CAJ-ZY99xZEsS5pCbZ7evi_ohozQBpHcNHDcXxfoeaLzuWRzyzw@mail.gmail.com>
2021-02-23 21:26 ` Arnd Bergmann
2021-02-23 21:54 ` Julian Braha [this message]
2021-02-23 22:05 ` Arnd Bergmann
2021-02-24 10:04 ` Leon Romanovsky
2021-03-01 18:48 ` Jason Gunthorpe
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=10464303.FBcTZR2von@ubuntu-mate-laptop \
--to=julianbraha@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=zyjzyj2000@gmail.com \
/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.