All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ctalbott-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	rni-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCHSET] block: cosmetic updates to blkcg API
Date: Fri, 20 Apr 2012 10:10:05 +0200	[thread overview]
Message-ID: <20120420081004.GH7505@kernel.dk> (raw)
In-Reply-To: <1334609847-12747-1-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

On Mon, Apr 16 2012, Tejun Heo wrote:
> Hello,
> 
> With recent blkcg updates, any out-of-tree change is already way
> broken and it's a good time to clean up blkcg API for more
> consistency.  This patchset makes a series of mostly cosmetic changes
> in an attempt to make the blkcg API easier on the eyes.
> 
> This is finally the last patchset of the long blkcg API update effort.
> I think that we now have something which at least is sane & logical
> and can be improved incrementally without having to be turned upside
> down.  My thanks to everyone involved for enduring the boring and
> rather painful process.
> 
> This patchset contains the following six patches.
> 
> 0001-blkcg-blkg_rwstat_read-was-missing-inline.patch
> 0002-blkcg-remove-blkio_group-path.patch
> 0003-blkcg-style-cleanups-for-blk-cgroup.h.patch
> 0004-blkcg-mass-rename-of-blkcg-API.patch
> 0005-blkcg-embed-struct-blkg_policy_data-in-policy-specif.patch
> 0006-blkcg-collapse-blkcg_policy_ops-into-blkcg_policy.patch
> 
> Other than 0002 which removes blkg->path[], none of the patches makes
> any functional difference.
> 
> This patchset is on top of
> 
>   block/for-3.5/core 5bc4afb1ec "blkcg: drop BLKCG_STAT_{PRIV|POL|OFF} macros"
> + [1] [PATCHSET] block: per-queue policy activation, take#2

Applied, thanks.

-- 
Jens Axboe

      parent reply	other threads:[~2012-04-20  8:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 20:57 [PATCHSET] block: cosmetic updates to blkcg API Tejun Heo
     [not found] ` <1334609847-12747-1-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2012-04-16 20:57   ` [PATCH 1/6] blkcg: blkg_rwstat_read() was missing inline Tejun Heo
2012-04-16 20:57   ` [PATCH 2/6] blkcg: remove blkio_group->path[] Tejun Heo
2012-04-16 20:57   ` Tejun Heo
2012-04-16 20:57   ` [PATCH 3/6] blkcg: style cleanups for blk-cgroup.h Tejun Heo
2012-04-16 20:57   ` Tejun Heo
2012-04-16 20:57   ` [PATCH 4/6] blkcg: mass rename of blkcg API Tejun Heo
2012-04-16 20:57   ` Tejun Heo
2012-04-16 20:57   ` [PATCH 5/6] blkcg: embed struct blkg_policy_data in policy specific data Tejun Heo
2012-04-16 20:57   ` Tejun Heo
2012-04-16 20:57   ` [PATCH 6/6] blkcg: collapse blkcg_policy_ops into blkcg_policy Tejun Heo
2012-04-16 20:57   ` Tejun Heo
2012-04-20  8:10   ` 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=20120420081004.GH7505@kernel.dk \
    --to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ctalbott-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=rni-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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.