From: Jason Gunthorpe <jgg@ziepe.ca>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [Bug 210021] New: IB/rxe: build error due to unmet dependency for CRYPTO_CRC32 by RDMA_RXE
Date: Tue, 3 Nov 2020 11:30:54 -0400 [thread overview]
Message-ID: <20201103153054.GN36674@ziepe.ca> (raw)
In-Reply-To: <CAD=hENcffzhy5ACO2TqH0t57uJQ3fG7B5e2few++niB9Xd9M-Q@mail.gmail.com>
On Tue, Nov 03, 2020 at 10:30:50PM +0800, Zhu Yanjun wrote:
> On Tue, Nov 3, 2020 at 7:33 PM <bugzilla-daemon@bugzilla.kernel.org> wrote:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=210021
> >
> > Bug ID: 210021
> > Summary: IB/rxe: build error due to unmet dependency for
> > CRYPTO_CRC32 by RDMA_RXE
> > Product: Drivers
> > Version: 2.5
> > Kernel Version: 5.4.4
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: Infiniband/RDMA
> > Assignee: drivers_infiniband-rdma@kernel-bugs.osdl.org
> > Reporter: fazilyildiran@gmail.com
> > CC: dledford@redhat.com, fazilyildiran@gmail.com,
> > leon@leon.nu, paul@pgazz.com
> > Regression: No
> >
> > Created attachment 293417
> > reproduce.tar.gz
> >
> > Attachment (reproduce.tar.gz) content:
> > - sample.config: Config file to reproduce the bug.
> > - build_out.txt: Output of Kbuild including the error messages.
> >
> > When RDMA_RXE is enabled and CRYPTO is disabled, it results in the
> > following Kbuild warning:
> >
> > WARNING: unmet direct dependencies detected for CRYPTO_CRC32
>
> https://lkml.org/lkml/2020/9/15/360
>
> Please check this mail thread.
>
> The discussion is in the above link.
I'd like crypto people to weight on what is proper here
Jason
prev parent reply other threads:[~2020-11-03 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 11:32 [Bug 210021] New: IB/rxe: build error due to unmet dependency for CRYPTO_CRC32 by RDMA_RXE bugzilla-daemon
2020-11-03 14:30 ` Zhu Yanjun
2020-11-03 15:30 ` Jason Gunthorpe [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=20201103153054.GN36674@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox