All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:netfs-next 26/26] fs/netfs/buffered_read.c:223:6: warning: no previous prototype for 'netfs_mark_read_submission'
Date: Sat, 28 Mar 2026 07:07:59 +0800	[thread overview]
Message-ID: <202603280644.RdtevT28-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-next
head:   13e05ee43d1290bb487ef5318b4d2d27be8ce4b5
commit: 13e05ee43d1290bb487ef5318b4d2d27be8ce4b5 [26/26] netfs: Combine prepare and issue ops and grab the buffers on request
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20260328/202603280644.RdtevT28-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260328/202603280644.RdtevT28-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/202603280644.RdtevT28-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> fs/netfs/buffered_read.c:223:6: warning: no previous prototype for 'netfs_mark_read_submission' [-Wmissing-prototypes]
     223 | void netfs_mark_read_submission(struct netfs_io_subrequest *subreq)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/netfs/buffered_read.c: In function 'netfs_mark_read_submission':
>> fs/netfs/buffered_read.c:226:33: warning: unused variable 'stream' [-Wunused-variable]
     226 |         struct netfs_io_stream *stream = &rreq->io_streams[0];
         |                                 ^~~~~~


vim +/netfs_mark_read_submission +223 fs/netfs/buffered_read.c

   213	
   214	/**
   215	 * netfs_mark_read_submission - Mark a read subrequest as being ready for submission
   216	 * @subreq: The subrequest to be marked
   217	 *
   218	 * Calling this marks a read subrequest as being ready for submission and makes
   219	 * it available to the collection thread.  After calling this, the filesystem's
   220	 * ->issue_read() method must invoke netfs_read_subreq_terminated() to end the
   221	 * subrequest.
   222	 */
 > 223	void netfs_mark_read_submission(struct netfs_io_subrequest *subreq)
   224	{
   225		struct netfs_io_request *rreq = subreq->rreq;
 > 226		struct netfs_io_stream *stream = &rreq->io_streams[0];
   227	
   228		_enter("R=%08x[%x]", rreq->debug_id, subreq->debug_index);
   229	
   230		trace_netfs_sreq(subreq, netfs_sreq_trace_submit);
   231	}
   232	EXPORT_SYMBOL(netfs_mark_read_submission);
   233	

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

                 reply	other threads:[~2026-03-27 23:08 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=202603280644.RdtevT28-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --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.