From: Tatyana Brokhman <tlinder@codeaurora.org>
To: axboe@kernel.dk
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Tatyana Brokhman <tlinder@codeaurora.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [RFC/PATCH 1/2] block: Expose kblock_schedule_delayed_work()
Date: Sun, 5 Aug 2012 14:30:40 +0300 [thread overview]
Message-ID: <1344166241-18708-2-git-send-email-tlinder@codeaurora.org> (raw)
In-Reply-To: <1344166241-18708-1-git-send-email-tlinder@codeaurora.org>
This function is exported in blk-core.c to be used in other modules
but it's definition in h file is missing.
Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
---
include/linux/blkdev.h | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index dc63297..ac0d069 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -1208,6 +1208,8 @@ static inline void put_dev_sector(Sector p)
struct work_struct;
int kblockd_schedule_work(struct request_queue *q, struct work_struct *work);
+int kblockd_schedule_delayed_work(struct request_queue *q,
+ struct delayed_work *dwork, unsigned long delay);
#ifdef CONFIG_BLK_CGROUP
/*
--
1.7.6
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-08-05 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 11:30 [RFC/PATCH 0/2] ROW scheduling Algorithm Tatyana Brokhman
2012-08-05 11:30 ` Tatyana Brokhman [this message]
2012-08-05 11:30 ` [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm Tatyana Brokhman
2012-08-06 16:35 ` Jeff Moyer
2012-08-07 11:28 ` Tanya Brokhman
2012-09-19 5:29 ` Jan Engelhardt
2012-08-08 7:27 ` [RFC/PATCH 0/2] ROW scheduling Algorithm Jaehoon Chung
2012-08-08 10:37 ` Tanya Brokhman
2012-08-08 11:57 ` Jaehoon Chung
2012-08-09 5:06 ` Tanya Brokhman
2012-08-14 19:09 ` Jae hoon Chung
2012-08-20 8:44 ` Seungwon Jeon
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=1344166241-18708-2-git-send-email-tlinder@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=axboe@kernel.dk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@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).