From: Yury Norov <yury.norov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Alexey Klimov" <aklimov@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"David Laight" <David.Laight@aculab.com>,
"Dennis Zhou" <dennis@kernel.org>,
"Emil Renner Berthing" <kernel@esmil.dk>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Joe Perches" <joe@perches.com>,
"Matti Vaittinen" <matti.vaittinen@fi.rohmeurope.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: Pull request for bitmap branch
Date: Sun, 27 Mar 2022 19:45:22 -0700 [thread overview]
Message-ID: <YkEhQiJkFmCLeYy6@yury-laptop> (raw)
In-Reply-To: <20220328131756.5aa6b7aa@canb.auug.org.au>
On Mon, Mar 28, 2022 at 01:17:56PM +1100, Stephen Rothwell wrote:
> Hi Yury,
>
> On Sun, 27 Mar 2022 18:09:51 -0700 Yury Norov <yury.norov@gmail.com> wrote:
> >
> > Can you please pull this branch for linux-next?
> > https://github.com/norov/linux/tree/bitmap
>
> Normally, I don't add new branches to linux-next during the merge
> window. An exception is for branches that only contain changes meant
> to be merged by Linus during the current merge window. Even then, this
> is very late to the table :-(
OK. I'll send a reminder when the window will be closed.
> Also, you should tell me the branch name I need to fetch (which I will
> refetch every day, so it should be a good stable name - like
> "for-next"), and if this branch will be merged directly by Linus, or
> through some other tree.
I'll rename it to 'bitmap-for-next'. Thanks.
> OK, I just checked ... the above URL is not a git tree. I suspect you
> meant me to fetch the "bitmap" branch of
> https://github.com/norov/linux.git, right?
Yes
> One more thing, that branch is based on Linus' tree of today, so really
> cannot have received much testing in its current form :-(
Rebasing this series from 5.17 to origin/master causes a couple merge
conflicts, so I decided to simplify your work.
Are you OK if I rebase it on 5.18-rc1 when it will be created and send
new request?
Thanks,
Yury
next prev parent reply other threads:[~2022-03-28 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 1:09 Yury Norov
2022-03-28 2:17 ` Stephen Rothwell
2022-03-28 2:45 ` Yury Norov [this message]
2022-03-28 3:22 ` Stephen Rothwell
2022-04-17 21:12 Yury Norov
2022-04-18 1:31 ` 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=YkEhQiJkFmCLeYy6@yury-laptop \
--to=yury.norov@gmail.com \
--cc=David.Laight@aculab.com \
--cc=aklimov@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dennis@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel@esmil.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mchehab@kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®