mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: agk@redhat.com, dm-devel@redhat.com,
	linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH] dm-ioband-v1.12.3: I/O bandwidth controller
Date: Thu, 20 Aug 2009 12:37:41 +1000	[thread overview]
Message-ID: <20090820023740.GA12528@verge.net.au> (raw)
In-Reply-To: <20090807.103640.104065157.ryov@valinux.co.jp>

On Fri, Aug 07, 2009 at 10:36:40AM +0900, Ryo Tsuruta wrote:
> Hi Alasdair,
> 
> Ryo Tsuruta <ryov@valinux.co.jp> wrote:
> > Hi Alasdair,
> > 
> > This is dm-ioband v1.12.3 release that is a minor update to avoid
> > sparse warnings other than related to the event tracing. (I used
> > sparse-2009-07-29.)
> > 
> > This patch can be applied to the current dm-devel tree and 2.6.31-rc4,
> > so could you please replace dm-add-ioband.patch in your tree with this?
> > And I would appreciate it if you would let me know your thoughts about
> > merging dm-ioband to upstream.
> 
> The dm-ioband patch in the dm-devel tree is still older. Could you
> please update it with the new patch? And could you please let me know
> your thoughts about dm-ioband?

Hi Alasdiar,

I'm wondering if you see any problems with merging dm-ioband at this time.
I'm eager to address any such concerns.


      reply	other threads:[~2009-08-20  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31  4:03 Ryo Tsuruta
2009-08-07  1:36 ` Ryo Tsuruta
2009-08-20  2:37   ` Simon Horman [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=20090820023740.GA12528@verge.net.au \
    --to=horms@verge.net.au \
    --cc=agk@redhat.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryov@valinux.co.jp \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.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

all inboxes | Powered by JetHome®