From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Ming Lei <ming.lei@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the scsi-mkp tree
Date: Wed, 21 Apr 2021 16:03:04 +1000 [thread overview]
Message-ID: <20210421160304.2a2480d8@canb.auug.org.au> (raw)
In-Reply-To: <20210303170349.2165b7b2@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
Hi all,
On Wed, 3 Mar 2021 17:03:49 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the scsi-mkp tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/linux/blk-mq.h:395: warning: Function parameter or member 'set_rq_budget_token' not described in 'blk_mq_ops'
> include/linux/blk-mq.h:395: warning: Function parameter or member 'get_rq_budget_token' not described in 'blk_mq_ops'
>
> Introduced by commit
>
> 9dda23635dbe ("scsi: blk-mq: Add callbacks for storing & retrieving budget token")
This is now commit
d022d18c045f ("scsi: blk-mq: Add callbacks for storing & retrieving budget token")
in the scsi tree and I am still seeing these warnings (as of next-20210420).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-21 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 6:03 linux-next: build warnings after merge of the scsi-mkp tree Stephen Rothwell
2021-04-21 6:03 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 5:06 Stephen Rothwell
2023-10-16 15:25 ` Mike Christie
2023-10-17 0:27 ` Martin K. Petersen
2018-02-13 3:00 Stephen Rothwell
2017-06-28 5:55 Stephen Rothwell
2017-06-29 5:07 ` Stephen Rothwell
2017-06-29 18:35 ` Madhani, Himanshu
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=20210421160304.2a2480d8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
/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).