All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jirislaby:devel 15/79] drivers/tty/tty_io.c:1152:5: error: conflicting types for 'tty_send_xchar'; have 'int(struct tty_struct *, u8)' {aka 'int(struct tty_struct *, unsigned char)'}
Date: Fri, 3 Nov 2023 23:38:10 +0800	[thread overview]
Message-ID: <202311032318.2MP4TsV1-lkp@intel.com> (raw)

Hi Jiri,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head:   0c245952ee3106fad8a2fd3198a8e5c324e90992
commit: 44f1bce172713e922fd4fe273ad8d29e1a3e9321 [15/79] tty: make tty_operations::send_xchar accept u8 char
config: csky-randconfig-001-20231103 (https://download.01.org/0day-ci/archive/20231103/202311032318.2MP4TsV1-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231103/202311032318.2MP4TsV1-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/202311032318.2MP4TsV1-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/tty/tty_io.c:1152:5: error: conflicting types for 'tty_send_xchar'; have 'int(struct tty_struct *, u8)' {aka 'int(struct tty_struct *, unsigned char)'}
    1152 | int tty_send_xchar(struct tty_struct *tty, u8 ch)
         |     ^~~~~~~~~~~~~~
   In file included from drivers/tty/tty_io.c:76:
   include/linux/tty.h:413:5: note: previous declaration of 'tty_send_xchar' with type 'int(struct tty_struct *, char)'
     413 | int tty_send_xchar(struct tty_struct *tty, char ch);
         |     ^~~~~~~~~~~~~~


vim +1152 drivers/tty/tty_io.c

  1142	
  1143	/**
  1144	 * tty_send_xchar - send priority character
  1145	 * @tty: the tty to send to
  1146	 * @ch: xchar to send
  1147	 *
  1148	 * Send a high priority character to the tty even if stopped.
  1149	 *
  1150	 * Locking: none for xchar method, write ordering for write method.
  1151	 */
> 1152	int tty_send_xchar(struct tty_struct *tty, u8 ch)
  1153	{
  1154		bool was_stopped = tty->flow.stopped;
  1155	
  1156		if (tty->ops->send_xchar) {
  1157			down_read(&tty->termios_rwsem);
  1158			tty->ops->send_xchar(tty, ch);
  1159			up_read(&tty->termios_rwsem);
  1160			return 0;
  1161		}
  1162	
  1163		if (tty_write_lock(tty, false) < 0)
  1164			return -ERESTARTSYS;
  1165	
  1166		down_read(&tty->termios_rwsem);
  1167		if (was_stopped)
  1168			start_tty(tty);
  1169		tty->ops->write(tty, &ch, 1);
  1170		if (was_stopped)
  1171			stop_tty(tty);
  1172		up_read(&tty->termios_rwsem);
  1173		tty_write_unlock(tty);
  1174		return 0;
  1175	}
  1176	

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

                 reply	other threads:[~2023-11-03 15:39 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=202311032318.2MP4TsV1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jirislaby@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.