From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Adam Bratschi-Kaye <ark.email@gmail.com>,
Alex Gaynor <alex.gaynor@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Antonio Terceiro <antonio.terceiro@linaro.org>,
Boqun Feng <boqun.feng@gmail.com>,
Boris-Chengbiao Zhou <bobo1239@web.de>, Daniel Xu <dxu@dxuuu.xyz>,
Dariusz Sosnowski <dsosnowski@dsosnowski.pl>,
Douglas Su <d0u9.su@outlook.com>, Finn Behrens <me@kloenk.de>,
Gary Guo <gary@garyguo.net>, Jiri Olsa <jolsa@kernel.org>,
Jiri Olsa <jolsa@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Miguel Ojeda <ojeda@kernel.org>,
Sven Van Asbroeck <thesven73@gmail.com>,
Wedson Almeida Filho <wedsonaf@google.com>
Subject: Re: linux-next: manual merge of the rust tree with Linus' tree
Date: Fri, 5 Nov 2021 07:31:49 +1100 [thread overview]
Message-ID: <20211105073149.5bc4e8a7@canb.auug.org.au> (raw)
In-Reply-To: <CANiq72mLAc1OMTo6LBTy1bwxM_+BbrRSCNn1uKW0irezUXBFcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
Hi Miguel,
On Thu, 4 Nov 2021 13:19:22 +0100 Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Wed, Nov 3, 2021 at 10:01 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Oops, sorry about that. I have added it back from today.
>
> No worries! By the way, I will be rebasing soon to fix a build error
> that happened due to some changes in mainline, so the conflict will
> disappear.
I would suggest that you don't rebase if you are intending to submit to
Linus. Instead, do a test merge with his tree and fix the issue in the
merge and test that, then explain it all the in the pull request (but
ask him to pull your tree without the merge).
> > BTW, are you intending to submit the rust tree this merge window?
>
> That was the idea, but a few things need to be taken care of before.
> In any case, I was told to start submitting it every couple weeks or
> so, so I think Linus et. al. do not mind if it aligns to a merge
> window or not (though I might be wrong...).
Much better to do it in the merge window. Linus almost never takes new
features outside a merge window (but you could always ask him).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-04 20:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 3:19 linux-next: manual merge of the rust tree with Linus' tree Stephen Rothwell
2021-11-03 10:30 ` Miguel Ojeda
2021-11-03 21:01 ` Stephen Rothwell
2021-11-04 12:19 ` Miguel Ojeda
2021-11-04 20:31 ` Stephen Rothwell [this message]
2021-11-05 11:00 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2025-07-21 4:31 Stephen Rothwell
2025-07-21 8:23 ` Miguel Ojeda
2025-03-17 10:20 Stephen Rothwell
2025-03-17 19:37 ` Miguel Ojeda
2025-03-17 22:31 ` Stephen Rothwell
2025-03-17 22:35 ` Miguel Ojeda
2025-03-17 10:05 Stephen Rothwell
2025-03-17 19:36 ` Miguel Ojeda
2024-09-16 8:03 Stephen Rothwell
2024-09-16 8:12 ` Miguel Ojeda
2022-10-04 8:05 Stephen Rothwell
2022-09-12 7:24 Stephen Rothwell
2022-07-25 8:41 Stephen Rothwell
2022-07-25 8:52 ` Miguel Ojeda
2022-07-13 10:34 Stephen Rothwell
2022-07-13 10:50 ` Miguel Ojeda
2022-07-13 11:39 ` Peter Zijlstra
2022-07-15 1:13 ` Miguel Ojeda
2022-07-15 9:01 ` Peter Zijlstra
2022-07-15 11:01 ` Miguel Ojeda
2021-12-10 18:18 broonie
2021-07-19 6:16 Stephen Rothwell
2021-07-12 0:37 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=20211105073149.5bc4e8a7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alex.gaynor@gmail.com \
--cc=andrii@kernel.org \
--cc=antonio.terceiro@linaro.org \
--cc=ark.email@gmail.com \
--cc=bobo1239@web.de \
--cc=boqun.feng@gmail.com \
--cc=d0u9.su@outlook.com \
--cc=dsosnowski@dsosnowski.pl \
--cc=dxu@dxuuu.xyz \
--cc=gary@garyguo.net \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=me@kloenk.de \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=ojeda@kernel.org \
--cc=thesven73@gmail.com \
--cc=wedsonaf@google.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