linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Roxell <anders.roxell@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	martin.petersen@oracle.com,
	Stanley Chu <stanley.chu@mediatek.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 20
Date: Fri, 20 Dec 2019 12:55:10 +0100	[thread overview]
Message-ID: <CADYN=9JjqvNWEsHLW5+GgSvkUkuz_6iMpD=X4Vk6nLQXtXa2Dw@mail.gmail.com> (raw)
In-Reply-To: <20191220160639.3406a5de@canb.auug.org.au>

On Fri, 20 Dec 2019 at 06:06, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,

Hi all,

>
> News: There will be no linux-next releases until January 6 (unless I
> get very bored :-)).
>
> Changes since 20191219:

on arm64 I see this:

../drivers/scsi/ufs/ufs-mediatek.c: In function ‘ufs_mtk_setup_ref_clk’:
../drivers/scsi/ufs/ufs-mediatek.c:93:23: error: storage size of
‘res’ isn’t known
  struct arm_smccc_res res;
                       ^~~
../drivers/scsi/ufs/ufs-mediatek.c:21:2: error: implicit declaration
of function ‘arm_smccc_smc’
[-Werror=implicit-function-declaration]
  arm_smccc_smc(MTK_SIP_UFS_CONTROL, \
  ^~~~~~~~~~~~~
../drivers/scsi/ufs/ufs-mediatek.c:101:3: note: in expansion of macro
‘ufs_mtk_ref_clk_notify’
   ufs_mtk_ref_clk_notify(on, res);
   ^~~~~~~~~~~~~~~~~~~~~~
../drivers/scsi/ufs/ufs-mediatek.c:21:16: error:
‘MTK_SIP_UFS_CONTROL’ undeclared (first use in this function); did
you mean ‘TX_HIBERN8_CONTROL’?
  arm_smccc_smc(MTK_SIP_UFS_CONTROL, \
                ^~~~~~~~~~~~~~~~~~~
../drivers/scsi/ufs/ufs-mediatek.c:101:3: note: in expansion of macro
‘ufs_mtk_ref_clk_notify’
   ufs_mtk_ref_clk_notify(on, res);
   ^~~~~~~~~~~~~~~~~~~~~~
../drivers/scsi/ufs/ufs-mediatek.c:21:16: note: each undeclared
identifier is reported only once for each function it appears in
  arm_smccc_smc(MTK_SIP_UFS_CONTROL, \
                ^~~~~~~~~~~~~~~~~~~
../drivers/scsi/ufs/ufs-mediatek.c:101:3: note: in expansion of macro
‘ufs_mtk_ref_clk_notify’
   ufs_mtk_ref_clk_notify(on, res);
   ^~~~~~~~~~~~~~~~~~~~~~
../drivers/scsi/ufs/ufs-mediatek.c:93:23: warning: unused variable
‘res’ [-Wunused-variable]
  struct arm_smccc_res res;
                       ^~~
cc1: some warnings being treated as errors
make[4]: *** [../scripts/Makefile.build:266:
drivers/scsi/ufs/ufs-mediatek.o] Error 1
make[4]: Target '__build' not remade because of errors.
make[3]: *** [../scripts/Makefile.build:503: drivers/scsi/ufs] Error 2
make[3]: Target '__build' not remade because of errors.
make[2]: *** [../scripts/Makefile.build:503: drivers/scsi] Error 2
../drivers/staging/wilc1000/hif.c: In function ‘wilc_parse_join_bss_param’:
../drivers/staging/wilc1000/hif.c:574:45: warning: array subscript 2
is above array bounds of ‘u32[2]’ {aka ‘unsigned int[2]’}
[-Warray-bounds]
    param->akm_suites[i] = crypto->akm_suites[i] & 0xFF;
                           ~~~~~~~~~~~~~~~~~~^~~
make[2]: Target '__build' not remade because of errors.
make[1]: *** [/srv/jenkins/kernel/next/Makefile:1694: drivers] Error 2
make[1]: Target 'Image' not remade because of errors.
make[1]: Target 'modules' not remade because of errors.
make: *** [Makefile:179: sub-make] Error 2
make: Target 'Image' not remade because of errors.
make: Target 'modules' not remade because of errors.

Cheers,
Anders

  reply	other threads:[~2019-12-20 11:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  5:06 linux-next: Tree for Dec 20 Stephen Rothwell
2019-12-20 11:55 ` Anders Roxell [this message]
2019-12-21 18:45   ` Martin K. Petersen
2019-12-23 12:20     ` Anders Roxell
  -- strict thread matches above, loose matches on Subject: below --
2023-12-20  9:50 Stephen Rothwell
2022-12-20  0:21 Stephen Rothwell
2021-12-20 11:39 Stephen Rothwell
2018-12-20  8:42 Stephen Rothwell
2018-12-20 18:35 ` Guenter Roeck
2017-12-20  4:43 Stephen Rothwell
2016-12-20  1:55 Stephen Rothwell
2016-12-20 20:44 ` Paul Gortmaker
2013-12-20  6:25 Stephen Rothwell
2012-12-20  6:46 Stephen Rothwell
2011-12-20  8:10 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='CADYN=9JjqvNWEsHLW5+GgSvkUkuz_6iMpD=X4Vk6nLQXtXa2Dw@mail.gmail.com' \
    --to=anders.roxell@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=stanley.chu@mediatek.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).