On Tue, Mar 24, 2020 at 6:59 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > wt., 24 mar 2020 o 17:58 Linus Walleij <linus.walleij@xxxxxxxxxx> napisał(a): > > > > On Tue, Mar 24, 2020 at 1:34 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > > wt., 24 mar 2020 o 10:05 Linus Walleij <linus.walleij@xxxxxxxxxx> napisał(a): > > > > > > > > Hi Bartosz, > > > > > > > > On Tue, Mar 24, 2020 at 9:29 AM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > > > > > > > > this is the third and probably last batch of changes for v5.7 I picked up > > > > > into my tree. Details are in the signed tag. Please pull. > > > > > > > > Which rc is this based on? I got a bunch of unrelated changes, so > > > > I suppose I need to merge the right rc base to the devel branch > > > > first. > > > > > > > > Yours, > > > > Linus Walleij > > > > > > Hi Linus, > > > > > > this is rebased on top of your devel branch, so you should be able to > > > pull it alright. > > > > To me it looks like it is based on my for-next branch which is a > > mixdown branch that I create solely for inclusion into > > linux-next. > > > > Can you double-check? > > > > FWIW for-next is created like this: > > git checkout for-next > > git reset --hard fixes > > git merge devel > > > > So that branch is highly volatile and not very good for > > development. > > > > Yours, > > Linus Walleij > > Hmm maybe I messed something up. What branch/tag do you want me to > rebase it on then to make it the most comfortable for you? v5.6-rc1 or my devel branch (e.g if you have some deps) works fine, thanks! :) I tend to base all next development on -rc1 unless there is some big bug fix, then I pull in some later -rc as well. Linus