All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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: Fri, 3 Sep 2021 02:20:55 +0800	[thread overview]
Message-ID: <20210902182053.GB26537@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <CAHk-=wi7gf_afYhx_PYCN-Sgghuw626dBNqxZ6aDQ-a+sg6wag@mail.gmail.com>

On Thu, Sep 02, 2021 at 09:18:59AM -0700, Linus Torvalds wrote:
> 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.

Yeah, thanks. That was my first time to merge another tree due to hard
dependency like this. I've gained some experience from this and will be
more confident on this if such things happen in the future. :)

Thanks,
Gao Xiang

> 
>          Linus

WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Peng Tao <tao.peng@linux.alibaba.com>,
	Miao Xie <miaoxie@huawei.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Joseph Qi <joseph.qi@linux.alibaba.com>,
	Yue Hu <huyue2@yulong.com>, Liu Bo <bo.liu@linux.alibaba.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Liu Jiang <gerry@linux.alibaba.com>,
	linux-erofs@lists.ozlabs.org
Subject: Re: [GIT PULL] erofs updates for 5.15-rc1
Date: Fri, 3 Sep 2021 02:20:55 +0800	[thread overview]
Message-ID: <20210902182053.GB26537@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <CAHk-=wi7gf_afYhx_PYCN-Sgghuw626dBNqxZ6aDQ-a+sg6wag@mail.gmail.com>

On Thu, Sep 02, 2021 at 09:18:59AM -0700, Linus Torvalds wrote:
> 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.

Yeah, thanks. That was my first time to merge another tree due to hard
dependency like this. I've gained some experience from this and will be
more confident on this if such things happen in the future. :)

Thanks,
Gao Xiang

> 
>          Linus

  reply	other threads:[~2021-09-02 18:21 UTC|newest]

Thread overview: 10+ 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-08-31 22:59 ` Gao Xiang
2021-09-02 16:18 ` Linus Torvalds
2021-09-02 16:18   ` Linus Torvalds
2021-09-02 18:20   ` Gao Xiang [this message]
2021-09-02 18:20     ` Gao Xiang
2021-09-02 18:57     ` Linus Torvalds
2021-09-02 18:57       ` Linus Torvalds
2021-09-02 17:37 ` pr-tracker-bot
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=20210902182053.GB26537@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=xiang@kernel.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 \
    --cc=torvalds@linux-foundation.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.