Message ID | 20211001181245.228419-1-yury.norov@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Resend bitmap patches | expand |
Hi Yury, On Fri, 1 Oct 2021 11:12:29 -0700 Yury Norov <yury.norov@gmail.com> wrote: > > Can you please take this series into the next tree? It has been already > in next-tree for 5.14: > > https://lore.kernel.org/linux-mmc/YSeduU41Ef568xhS@alley/T/ > > But it was damaged and we decided to merge it in 5.15 cycle. No changes > comparing to 5.14, except for Andy's patch that was already upstreamed > and therefore removed from here. > > The git tree is here: > https://github.com/norov/linux/tree/bitmap-20210929 Sorry, I cannot include that in linux-next since it it based on (an old version of) linux-next itself. If it needs to be based on other trees in linux-next, then it has to be added to Andrew Morton's patch series (in the post linux-next section. Otherwise, if it can be based on Linus Torvald's tree (even with a few conflicts), then that is better.
On Sun, Oct 03, 2021 at 09:47:22AM +1100, Stephen Rothwell wrote: > Hi Yury, > > On Fri, 1 Oct 2021 11:12:29 -0700 Yury Norov <yury.norov@gmail.com> wrote: > > > > Can you please take this series into the next tree? It has been already > > in next-tree for 5.14: > > > > https://lore.kernel.org/linux-mmc/YSeduU41Ef568xhS@alley/T/ > > > > But it was damaged and we decided to merge it in 5.15 cycle. No changes > > comparing to 5.14, except for Andy's patch that was already upstreamed > > and therefore removed from here. > > > > The git tree is here: > > https://github.com/norov/linux/tree/bitmap-20210929 > > Sorry, I cannot include that in linux-next since it it based on (an old > version of) linux-next itself. If it needs to be based on other trees in > linux-next, then it has to be added to Andrew Morton's patch series (in > the post linux-next section. Otherwise, if it can be based on Linus > Torvald's tree (even with a few conflicts), then that is better. Ok, I'll resend it based on Linus tree shortly Thanks, Yury
Hi Yury, On Sat, 2 Oct 2021 16:10:20 -0700 Yury Norov <yury.norov@gmail.com> wrote: > > Ok, I'll resend it based on Linus tree shortly Thanks. I also need a branch name that will stay the same. I will fetch that branch every day and use whatever you have set that branch to. Here are the rules for inclusion in linux-next: You will need to ensure that the commits in your tree/branch have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Hi Yury, On Sat, 2 Oct 2021 16:10:20 -0700 Yury Norov <yury.norov@gmail.com> wrote: > > Ok, I'll resend it based on Linus tree shortly There is no big hurry, the next linux-next release will not be until Tuesday (my time). So you have time to retest after the rebase.