linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the iio tree
Date: Fri, 1 Jul 2022 11:43:45 +0100	[thread overview]
Message-ID: <20220701114345.00002713@Huawei.com> (raw)
In-Reply-To: <20220701182849.124d8cd1@canb.auug.org.au>

On Fri, 1 Jul 2022 18:28:49 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> On Fri, 1 Jul 2022 15:29:44 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> \> 
> > After merging the iio tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> > 
> > WARNING: modpost: module qcom-spmi-adc-tm5 uses symbol qcom_adc_tm5_temp_volt_scale from namespace IIO_QCOM_VADC, but does not import it.
> > WARNING: modpost: module qcom-spmi-adc-tm5 uses symbol qcom_adc5_prescaling_from_dt from namespace IIO_QCOM_VADC, but does not import it.
> > WARNING: modpost: module qcom-spmi-adc-tm5 uses symbol qcom_adc5_hw_settle_time_from_dt from namespace IIO_QCOM_VADC, but does not import it.
> > WARNING: modpost: module qcom-spmi-adc-tm5 uses symbol qcom_adc5_avg_samples_from_dt from namespace IIO_QCOM_VADC, but does not import it.
> > WARNING: modpost: module qcom-spmi-adc-tm5 uses symbol qcom_adc5_decimation_from_dt from namespace IIO_QCOM_VADC, but does not import it.
> > 
> > Introduced by commit
> > 
> >   ec9b269f61cc ("iio: adc: qcom-vadc: Move symbol exports to IIO_QCOM_VADC namespace")  
> 
> This became a build failure in the arm64 defconfig build, so I have
> reverted that commit for today.
> 

As the original patch didn't have any thermal related parts / review, I've dropped
it for now rather than fixing up.  Will circle round with a new version in due time.

Thanks,

Jonathan

  parent reply	other threads:[~2022-07-01 10:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01  5:29 linux-next: build warning after merge of the iio tree Stephen Rothwell
2022-07-01  8:28 ` Stephen Rothwell
2022-07-01  9:28   ` Jonathan Cameron
2022-07-01 10:43   ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  2:41 Stephen Rothwell
2025-04-15  6:28 Stephen Rothwell
2025-04-15  7:35 ` Angelo Dureghello
2024-11-07 11:40 Stephen Rothwell
2024-11-07 12:25 ` Jonathan Cameron
2024-10-29  4:50 Stephen Rothwell
2024-10-29  9:43 ` Jonathan Cameron
2024-10-15  4:50 Stephen Rothwell
2024-08-20  3:47 Stephen Rothwell
2024-08-20  9:08 ` Jonathan Cameron
2024-06-05  3:34 Stephen Rothwell
2024-02-28  3:51 Stephen Rothwell
2022-04-28  7:37 Stephen Rothwell
2022-04-28  8:07 ` Miquel Raynal
2022-02-11  7:42 Stephen Rothwell

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=20220701114345.00002713@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).