Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190325135557.3423-1-axel.lin@ingics.com> <CAMRc=MfvguEhfqXBWa8o12WF6xbHM7yEiOZC+N01UDAQYQs7Zg@mail.gmail.com>
 <CAFRkauAkN=QAdqF4Qrq=PRS29yifLegrjPTU2=ngZtrkLbY58w@mail.gmail.com>
 <CAMRc=MeN4W3iOc5+t+9b7knRJVx8vA+eb95bRHFBGZJvC0ffuQ@mail.gmail.com> <CAFRkauDMj_5p7yviNYsymj7P_qPfFC1crhiP5ouwEnp7jt_rPg@mail.gmail.com>
In-Reply-To: <CAFRkauDMj_5p7yviNYsymj7P_qPfFC1crhiP5ouwEnp7jt_rPg@mail.gmail.com>
From:   Bartosz Golaszewski <brgl@bgdev.pl>
Date:   Wed, 27 Mar 2019 15:00:25 +0100
Message-ID: <CAMRc=McRKEP1ro4tWkXbyJKRJeaab9HL1r4cj9H9XBjjA2r6vA@mail.gmail.com>
Subject: Re: [PATCH] regulator: max77650: Convert MAX77651 SBB1 to pickable
 linear range
To:     Axel Lin <axel.lin@ingics.com>
Cc:     Mark Brown <broonie@kernel.org>,
        Bartosz Golaszewski <bgolaszewski@baylibre.com>,
        Liam Girdwood <lgirdwood@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

=C5=9Br., 27 mar 2019 o 14:56 Axel Lin <axel.lin@ingics.com> napisa=C5=82(a=
):
>
> Bartosz Golaszewski <brgl@bgdev.pl> =E6=96=BC 2019=E5=B9=B43=E6=9C=8827=
=E6=97=A5 =E9=80=B1=E4=B8=89 =E4=B8=8B=E5=8D=889:08=E5=AF=AB=E9=81=93=EF=BC=
=9A
> >
> > =C5=9Br., 27 mar 2019 o 11:17 Axel Lin <axel.lin@ingics.com> napisa=C5=
=82(a):
> > >
> > > > Hi,
> > > >
> > > > what tree is this patch based on, because it doesn't apply on top o=
f v5.1-rc2.
> > > Hi Bart,
> > > You can use linux-next or regulator tree.
> > > However,  due to build dependency you need to manually apply max77650
> > > mfd drvier manually  because it's not exist in these tree.
> > >
> > > Alternatively, you can check the difference of your tree with
> > > linux-next regarding max77650-regulator.c changes.
> > > Then pickup related patches first so you can cleanly apply this patch=
.
> > >
> > > Regards,
> > > Axel
> >
> > Can you push a branch you used somewhere public? It'll be faster that w=
ay.
> I don't have public git tree for linux-kernel.
> I think you should try linux-next tree, this patch can be applied to linu=
x-next.
> Other missing files should be all your patches:
> https://patchwork.kernel.org/cover/10809945/
>
> Regards,
> Axel

What do you mean you don't have a public git tree? Can't you create a
gitlab account and just push the tree there? Alternatively, given the
amount of patches you send, I doubt the kernel.org maintainers would
refuse if you asked for an account.

Frankly, this week is quite busy for me, so if you want me to play
with pulling random patches, then the test will have to wait until
next week.

Best regards,
Bartosz Golaszewski