All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [miquelraynal:ecc-engine 57/60] drivers/mtd/nand/ecc-mxic.c:155:32: sparse: sparse: symbol 'mxic_ecc_ooblayout_ops' was not declared. Should it be static?
Date: Sun, 19 Jan 2020 03:53:02 +0800	[thread overview]
Message-ID: <202001190345.FBc6FK9N%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

tree:   https://github.com/miquelraynal/linux-0day.git ecc-engine
head:   6864d344e2877ab874d2d2d1bee09cb7964342fd
commit: 907d0202f41f5586c4742ea320c2606c014abc4a [57/60] mtd: nand: mxic-ecc: Add Macronix external ECC engine support
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-131-g22978b6b-dirty
        git checkout 907d0202f41f5586c4742ea320c2606c014abc4a
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> drivers/mtd/nand/ecc-mxic.c:155:32: sparse: sparse: symbol 'mxic_ecc_ooblayout_ops' was not declared. Should it be static?
>> drivers/mtd/nand/ecc-mxic.c:605:5: sparse: sparse: symbol 'mxic_ecc_probe' was not declared. Should it be static?
>> drivers/mtd/nand/ecc-mxic.c:628:5: sparse: sparse: symbol 'mxic_ecc_remove' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

             reply	other threads:[~2020-01-18 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 19:53 kbuild test robot [this message]
2020-01-18 19:53 ` [RFC PATCH miquelraynal] mtd: nand: mxic-ecc: mxic_ecc_ooblayout_ops can be static kbuild test robot

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=202001190345.FBc6FK9N%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.