From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Chao Yu <chao@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-erofs@lists.ozlabs.org,
Dan Williams <dan.j.williams@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Huang Jianan <huangjianan@oppo.com>, Yue Hu <huyue2@yulong.com>,
Miao Xie <miaoxie@huawei.com>, Liu Bo <bo.liu@linux.alibaba.com>,
Peng Tao <tao.peng@linux.alibaba.com>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Liu Jiang <gerry@linux.alibaba.com>
Subject: Re: [GIT PULL] erofs updates for 5.15-rc1
Date: Thu, 2 Sep 2021 09:18:59 -0700 [thread overview]
Message-ID: <CAHk-=wi7gf_afYhx_PYCN-Sgghuw626dBNqxZ6aDQ-a+sg6wag@mail.gmail.com> (raw)
In-Reply-To: <20210831225935.GA26537@hsiangkao-HP-ZHAN-66-Pro-G1>
On Tue, Aug 31, 2021 at 4:00 PM Gao Xiang <xiang@kernel.org> wrote:
>
> All commits have been tested and have been in linux-next. Note that
> in order to support iomap tail-packing inline, I had to merge iomap
> core branch (I've created a merge commit with the reason) in advance
> to resolve such functional dependency, which is now merged into
> upstream. Hopefully I did the right thing...
It all looks fine to me. You have all the important parts: what you
are merging, and _why_ you are merging it.
So no complaints, and thanks for making it explicit in your pull
request too so that I'm not taken by surprise.
Linus
next prev parent reply other threads:[~2021-09-02 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 22:59 [GIT PULL] erofs updates for 5.15-rc1 Gao Xiang
2021-09-02 16:18 ` Linus Torvalds [this message]
2021-09-02 18:20 ` Gao Xiang
2021-09-02 18:57 ` Linus Torvalds
2021-09-02 17:37 ` pr-tracker-bot
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='CAHk-=wi7gf_afYhx_PYCN-Sgghuw626dBNqxZ6aDQ-a+sg6wag@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bo.liu@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gerry@linux.alibaba.com \
--cc=huangjianan@oppo.com \
--cc=huyue2@yulong.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=sfr@canb.auug.org.au \
--cc=tao.peng@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).