All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/2 v3] blktrace: Fix sparse annotations and warn if enabling multiple traces
Date: Mon, 8 Jun 2020 14:01:02 +0000	[thread overview]
Message-ID: <20200608140102.GO11244@42.do-not-panic.com> (raw)
In-Reply-To: <20200608082528.GK13248@quack2.suse.cz>

On Mon, Jun 08, 2020 at 10:25:28AM +0200, Jan Kara wrote:
> BTW the two patches applied just fine separately from the rest of
> the series so I don't think there's any dependency to the rest of your
> series even in context.

The depndency was just minor contextual edits, which can be fixed with
a rebase, I've done that now, so this is good to go in first. I'll skip
these two patches fromy series then.

  Luis

  reply	other threads:[~2020-06-08 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 14:58 [PATCH 0/2 v3] blktrace: Fix sparse annotations and warn if enabling multiple traces Jan Kara
2020-06-05 14:58 ` [PATCH 1/2] blktrace: break out of blktrace setup on concurrent calls Jan Kara
2020-06-08  6:45   ` Chaitanya Kulkarni
2020-06-05 14:58 ` [PATCH 2/2] blktrace: Avoid sparse warnings when assigning q->blk_trace Jan Kara
2020-06-08  6:46   ` Chaitanya Kulkarni
2020-06-05 15:03 ` [PATCH 0/2 v3] blktrace: Fix sparse annotations and warn if enabling multiple traces Luis Chamberlain
2020-06-08  8:25   ` Jan Kara
2020-06-08 14:01     ` Luis Chamberlain [this message]
2020-06-17 12:51 ` Jan Kara
2020-06-17 15:07   ` Jens Axboe

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=20200608140102.GO11244@42.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --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.