netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vadim Fedorenko <vadfed@meta.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Jakub Kicinski <kuba@kernel.org>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Jiri Slaby <jirislaby@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] ptp: ocp: adjust sysfs entries to expose tty information
Date: Fri, 16 Aug 2024 20:03:06 +0800	[thread overview]
Message-ID: <202408161934.aQsUDy88-lkp@intel.com> (raw)
In-Reply-To: <20240815125905.1667148-1-vadfed@meta.com>

Hi Vadim,

kernel test robot noticed the following build warnings:

[auto build test WARNING on net/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Vadim-Fedorenko/docs-ABI-update-OCP-TimeCard-sysfs-entries/20240815-210131
base:   net/main
patch link:    https://lore.kernel.org/r/20240815125905.1667148-1-vadfed%40meta.com
patch subject: [PATCH net v3 1/2] ptp: ocp: adjust sysfs entries to expose tty information
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20240816/202408161934.aQsUDy88-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240816/202408161934.aQsUDy88-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/202408161934.aQsUDy88-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/ptp/ptp_ocp.c: In function 'ptp_ocp_tty_show':
>> drivers/ptp/ptp_ocp.c:3360:37: warning: unused variable 'port' [-Wunused-variable]
    3360 |         struct ptp_ocp_serial_port *port;
         |                                     ^~~~


vim +/port +3360 drivers/ptp/ptp_ocp.c

  3354	
  3355	static ssize_t
  3356	ptp_ocp_tty_show(struct device *dev, struct device_attribute *attr, char *buf)
  3357	{
  3358		struct dev_ext_attribute *ea = to_ext_attr(attr);
  3359		struct ptp_ocp *bp = dev_get_drvdata(dev);
> 3360		struct ptp_ocp_serial_port *port;
  3361	
  3362		return sysfs_emit(buf, "ttyS%d", bp->port[(uintptr_t)ea->var].line);
  3363	}
  3364	

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

      parent reply	other threads:[~2024-08-16 12:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 12:59 [PATCH net v3 1/2] ptp: ocp: adjust sysfs entries to expose tty information Vadim Fedorenko
2024-08-15 12:59 ` [PATCH net v3 2/2] docs: ABI: update OCP TimeCard sysfs entries Vadim Fedorenko
2024-08-15 13:41 ` [PATCH net v3 1/2] ptp: ocp: adjust sysfs entries to expose tty information Greg Kroah-Hartman
2024-08-15 15:06   ` Vadim Fedorenko
2024-08-15 13:54 ` Simon Horman
2024-08-15 14:05   ` Vadim Fedorenko
2024-08-16  5:26 ` Jiri Slaby
2024-08-16 18:48   ` Vadim Fedorenko
2024-08-16 12:03 ` kernel test robot [this message]

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=202408161934.aQsUDy88-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vadfed@meta.com \
    --cc=vadim.fedorenko@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 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).