From: Christoph Hellwig <hch@infradead.org>
To: Umesh Patel <Umesh.Patel@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: blk_init_queue vs blk_alloc_queue
Date: Mon, 13 Mar 2017 06:36:29 -0700 [thread overview]
Message-ID: <20170313133629.GA29232@infradead.org> (raw)
In-Reply-To: <CY1PR0401MB1353F4C37A081FCB3E6E145EE1250@CY1PR0401MB1353.namprd04.prod.outlook.com>
On Mon, Mar 13, 2017 at 09:14:12AM +0000, Umesh Patel wrote:
> Hello,
>
> I Would like to know difference between blk_init_queue and blk_alloc_queue API.
> Can anyone explain when to use what ?
The short answer is that you should neither. The long answer is that
you should send a link to your driver source if you want anyone to help
you.
next prev parent reply other threads:[~2017-03-13 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 9:14 blk_init_queue vs blk_alloc_queue Umesh Patel
2017-03-13 13:36 ` Christoph Hellwig [this message]
2017-03-13 14:23 ` Umesh Patel
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=20170313133629.GA29232@infradead.org \
--to=hch@infradead.org \
--cc=Umesh.Patel@wdc.com \
--cc=linux-block@vger.kernel.org \
/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).