From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v2 0/3] block: drive-by cleanups for block cgroup
Date: Fri, 1 May 2020 00:03:53 +0900 [thread overview]
Message-ID: <20200430150356.35691-1-johannes.thumshirn@wdc.com> (raw)
While reviewing Christoph's bio cleanup series, I noticed
blkcg_bio_issue_check() is way too big for an inline function. When I moved it
into block/blk-cgroup.c I noticed two other functions which only have one or
no callers at all, so I cleaned them up as well.
Changes to v1:
- Re-based onto for-5.8/block with Christoph's patches
- Removed white-space to not hurt Christoph's feelings
- Added Reviewed-bys
Johannes Thumshirn (3):
block: remove blk_queue_root_blkg
block: move blkcg_bio_issue_check out of line
block: open-code blkg_path in it's sole caller
block/bfq-cgroup.c | 3 +-
block/blk-cgroup.c | 57 +++++++++++++++++++++++++
include/linux/blk-cgroup.h | 87 +-------------------------------------
3 files changed, 60 insertions(+), 87 deletions(-)
--
2.24.1
next reply other threads:[~2020-04-30 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 15:03 Johannes Thumshirn [this message]
2020-04-30 15:03 ` [PATCH v2 1/3] block: remove blk_queue_root_blkg Johannes Thumshirn
2020-04-30 15:03 ` [PATCH v2 2/3] block: move blkcg_bio_issue_check out of line Johannes Thumshirn
2020-04-30 15:03 ` [PATCH v2 3/3] block: open-code blkg_path in it's sole caller Johannes Thumshirn
2020-05-04 15:31 ` [PATCH v2 0/3] block: drive-by cleanups for block cgroup Johannes Thumshirn
2020-05-08 10:33 ` Johannes Thumshirn
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=20200430150356.35691-1-johannes.thumshirn@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--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 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.