From: Jens Axboe <axboe@kernel.dk>
To: Prasad Muppana <Lalita.Muppana@microsoft.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Praveen Kumar <kumarpraveen@linux.microsoft.com>,
Christoph Hellwig <hch@infradead.org>,
Atin Mukherjee <Atin.MUKHERJEE@microsoft.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"schakrabarti@linux.microsoft.com"
<schakrabarti@linux.microsoft.com>
Subject: Re: [PATCH] blk-mq: export blk_mq_submit_bio symbol
Date: Wed, 22 Sep 2021 08:29:28 -0600 [thread overview]
Message-ID: <36660d33-c02d-27ee-1332-4ea6e7126b88@kernel.dk> (raw)
In-Reply-To: <PSAP153MB0518090A749E26814966672684A29@PSAP153MB0518.APCP153.PROD.OUTLOOK.COM>
On 9/21/21 11:45 PM, Prasad Muppana wrote:
> Hi Chaitanya,
>
> Thanks for the response.
>
> Our driver code is not yet public and so Praveen has explained the
> flow of the code. Please let me know is there any other way to get
> some help here quickly.
The explanation, while appreciated, doesn't solve the problem here. We
_never_ add any exports for APIs that don't have any in-kernel users.
That's a hard rule that we've had forever. As such, there is not a path
for entry for this particular patch right now. It should be submitted
alongside the upstream submission request for the code using it, as a
preparatory patch.
--
Jens Axboe
prev parent reply other threads:[~2021-09-22 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 5:36 [PATCH] blk-mq: export blk_mq_submit_bio symbol Praveen Kumar
2021-09-09 5:48 ` Christoph Hellwig
2021-09-10 11:54 ` Praveen Kumar
2021-09-09 16:16 ` Chaitanya Kulkarni
2021-09-13 4:24 ` Praveen Kumar
2021-09-13 6:09 ` Christoph Hellwig
2021-09-13 7:03 ` Praveen Kumar
2021-09-20 5:30 ` Prasad Muppana
2021-09-20 20:25 ` Chaitanya Kulkarni
2021-09-22 5:45 ` Prasad Muppana
2021-09-22 14:29 ` Jens Axboe [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=36660d33-c02d-27ee-1332-4ea6e7126b88@kernel.dk \
--to=axboe@kernel.dk \
--cc=Atin.MUKHERJEE@microsoft.com \
--cc=Lalita.Muppana@microsoft.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@infradead.org \
--cc=kumarpraveen@linux.microsoft.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schakrabarti@linux.microsoft.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).