From: Alexandru Ardelean <ardeleanalex@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael Hennerich <michael.hennerich@analog.com>,
linux-iio <linux-iio@vger.kernel.org>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: linux-next: Tree for Mar 16 (AD9467 & ADI_AXI_ADC)
Date: Wed, 17 Mar 2021 10:16:01 +0200 [thread overview]
Message-ID: <CA+U=DspHhL=Of2axKW6FiF3oG8S7FEP4QBLEZHc5VQ4LzmvqNQ@mail.gmail.com> (raw)
In-Reply-To: <d3c9bca8-3709-3613-c4cd-6da2aa96c2b9@infradead.org>
On Tue, Mar 16, 2021 at 11:20 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 3/15/21 9:50 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > News: there will be no linux-next release on Friday this week.
> >
> > Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> > so please be careful if you are trying to bisect a bug.
> >
> > News: if your -next included tree is based on Linus' tree tag
> > v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> > consider rebasing it onto v5.12-rc2. Also, please check any branches
> > merged into your branch.
> >
> > Changes since 20210315:
>
>
> on i386 or x86_64:
>
> WARNING: unmet direct dependencies detected for ADI_AXI_ADC
> Depends on [n]: IIO [=y] && HAS_IOMEM [=y] && OF [=n]
> Selected by [y]:
> - AD9467 [=y] && IIO [=y] && SPI [=y]
>
>
> AD9467 should not select ADI_AXI_ADC when OF is not enabled,
> so possibly AD9467 should depend on OF.
Hmm, this becomes a bit complicated.
We got here because we needed to add a depends on HAS_IOMEM for the
ADI_AXI_ADC (due to the s390 arch).
Maybe a better fix would be for AD9467 to depend on ADI_AXI_ADC.
The AD9467 driver can't function without the ADI_AXI_ADC driver.
It is a little early to move this to a "high-speed ADC" subgroup.
>
>
> Full randconfig file is attached.
>
>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2021-03-17 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 4:50 linux-next: Tree for Mar 16 Stephen Rothwell
2021-03-16 18:34 ` linux-next: Tree for Mar 16 (AD9467 & ADI_AXI_ADC) Randy Dunlap
2021-03-17 8:16 ` Alexandru Ardelean [this message]
2021-03-18 18:44 ` Randy Dunlap
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='CA+U=DspHhL=Of2axKW6FiF3oG8S7FEP4QBLEZHc5VQ4LzmvqNQ@mail.gmail.com' \
--to=ardeleanalex@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=vilhelm.gray@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;
as well as URLs for NNTP newsgroup(s).