From: Jens Axboe <axboe@kernel.dk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: paulmck@kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>,
Frederic Weisbecker <frederic@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the rcu tree with the block tree
Date: Fri, 12 Feb 2021 09:26:28 -0700 [thread overview]
Message-ID: <793e83ff-3bd1-39a0-9037-cb3cbfb455e8@kernel.dk> (raw)
In-Reply-To: <YCaqSuQBhqgAkWLm@hirez.programming.kicks-ass.net>
On 2/12/21 9:18 AM, Peter Zijlstra wrote:
> On Fri, Feb 12, 2021 at 08:26:56AM -0700, Jens Axboe wrote:
>> But I think I made a mistake in that it should've been sched/smp instead,
>> which would likely get rid of this issue too? I'll rebase it, it's just
>> a single topic branch with just those two patches on top.
>
> Right, I made tip/sched/smp with just that one patch. That _should_ work
> for you, if not, please let me know.
It does, I just originally fat fingered the pull. All fixed up now!
--
Jens Axboe
next prev parent reply other threads:[~2021-02-12 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 5:48 linux-next: manual merge of the rcu tree with the block tree Stephen Rothwell
2021-02-11 17:38 ` Paul E. McKenney
2021-02-12 15:24 ` Frederic Weisbecker
2021-02-12 15:26 ` Jens Axboe
2021-02-12 16:18 ` Peter Zijlstra
2021-02-12 16:26 ` Jens Axboe [this message]
2021-02-12 15:18 ` Frederic Weisbecker
2021-02-12 15:30 ` Jens Axboe
2021-02-12 15:33 ` Frederic Weisbecker
2021-02-13 2:05 ` Stephen Rothwell
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=793e83ff-3bd1-39a0-9037-cb3cbfb455e8@kernel.dk \
--to=axboe@kernel.dk \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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