All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:5.15-2.2.x-imx 4263/27938] drivers/tty/serial/fsl_linflexuart.c:180:13: warning: 'linflex_string_write' used but never defined
Date: Sun, 3 Mar 2024 15:47:22 +0800	[thread overview]
Message-ID: <202403031513.avMTKobf-lkp@intel.com> (raw)

tree:   https://github.com/Freescale/linux-fslc 5.15-2.2.x-imx
head:   d761b18f6bc83bce94251467e3c0974243318456
commit: 093375dfcc1c685b974c21cb9b50f44df4dcf29f [4263/27938] LF-631-7 tty: serial: linflexuart: Add support for FIFO with DMA
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240303/202403031513.avMTKobf-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240303/202403031513.avMTKobf-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403031513.avMTKobf-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/tty/serial/fsl_linflexuart.c:180:13: warning: 'linflex_string_write' used but never defined
     180 | static void linflex_string_write(struct linflex_port *sport, const char *s,
         |             ^~~~~~~~~~~~~~~~~~~~


vim +/linflex_string_write +180 drivers/tty/serial/fsl_linflexuart.c

   176	
   177	/* Forward declare this for the dma callbacks. */
   178	static void linflex_dma_tx_complete(void *arg);
   179	static void linflex_dma_rx_complete(void *arg);
 > 180	static void linflex_string_write(struct linflex_port *sport, const char *s,
   181					 unsigned int count);
   182	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-03-03  7:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202403031513.avMTKobf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=otavio@ossystems.com.br \
    /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.