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: Fri, 5 Jun 2020 15:03:50 +0000 [thread overview]
Message-ID: <20200605150350.GM11244@42.do-not-panic.com> (raw)
In-Reply-To: <20200605145349.18454-1-jack@suse.cz>
On Fri, Jun 05, 2020 at 04:58:35PM +0200, Jan Kara wrote:
> Hello Jens,
>
> this series contains a patch from Luis' blktrace series and then my patch
> to fix sparse warnings in blktrace. Luis' patch stands on its own, was
> reviewed, and changes what I need to change as well so I've decided it's just
> simplest to pull it in with my patch.
Hey Jan,
Since these patches have contexts which can affect other patches in the
series of fixes I have, if possible I'd prefer if these get addressed in
order. I was just waiting for 0-day to finish grinding on the series.
I already have a successful build results, but just waiting on the
series of other tests, part of which include blktests.
If this is agreeable, I hope to post that series later today.
Luis
next prev parent reply other threads:[~2020-06-05 15:03 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 ` Luis Chamberlain [this message]
2020-06-08 8:25 ` [PATCH 0/2 v3] blktrace: Fix sparse annotations and warn if enabling multiple traces Jan Kara
2020-06-08 14:01 ` Luis Chamberlain
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=20200605150350.GM11244@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 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).