From: Jens Axboe <axboe@kernel•dk>
To: Tetsuo Handa <penguin-kernel@i-love•sakura.ne.jp>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Christoph Hellwig <hch@lst•de>,
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 tomoyo tree with the block tree
Date: Tue, 23 Nov 2021 19:38:51 -0700 [thread overview]
Message-ID: <353a1ef2-df1e-21f1-b27d-8ff940279299@kernel.dk> (raw)
In-Reply-To: <b5d2fbb7-5bc6-f0c1-0869-1c3e7096677e@i-love.sakura.ne.jp>
On 11/23/21 7:25 PM, Tetsuo Handa wrote:
> On 2021/11/24 11:06, Jens Axboe wrote:
>>
>> Why does the tomoyo tree have loop commits is the question?
>>
>
> I'm testing patches using my tree until maintainers respond.
It's a week old, please don't put patches from an unrelated tree
into a different tree.
--
Jens Axboe
prev parent reply other threads:[~2021-11-24 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 0:38 linux-next: manual merge of the tomoyo tree with the block tree Stephen Rothwell
2021-11-24 2:06 ` Jens Axboe
2021-11-24 2:25 ` Tetsuo Handa
2021-11-24 2:38 ` 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=353a1ef2-df1e-21f1-b27d-8ff940279299@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=penguin-kernel@i-love$(echo .)sakura.ne.jp \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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