From: Gao Xiang <email@example.com> To: Linus Torvalds <firstname.lastname@example.org> Cc: Stephen Rothwell <email@example.com>, Peng Tao <firstname.lastname@example.org>, Miao Xie <email@example.com>, LKML <firstname.lastname@example.org>, Joseph Qi <email@example.com>, Yue Hu <firstname.lastname@example.org>, Liu Bo <email@example.com>, linux-fsdevel <firstname.lastname@example.org>, Dan Williams <email@example.com>, Liu Jiang <firstname.lastname@example.org>, email@example.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-Sgghuw626dBNqxZ6aDQfirstname.lastname@example.org> On Thu, Sep 02, 2021 at 09:18:59AM -0700, Linus Torvalds wrote: > On Tue, Aug 31, 2021 at 4:00 PM Gao Xiang <email@example.com> 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
next prev parent reply other threads:[~2021-09-02 18:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-31 22:59 Gao Xiang 2021-09-02 16:18 ` Linus Torvalds 2021-09-02 18:20 ` Gao Xiang [this message] 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=20210902182053.GB26537@hsiangkao-HP-ZHAN-66-Pro-G1 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [GIT PULL] erofs updates for 5.15-rc1' \ /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
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).