linux-kernel - Re: [PATCH] regulator: max77650: Convert MAX77651 SBB1 to pickable linear range

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 27 Mar 2019 15:00:25 +0100
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: max77650: Convert MAX77651 SBB1 to pickable
 linear range

śr., 27 mar 2019 o 14:56 Axel Lin <axel.lin@...ics.com> napisał(a):
>
> Bartosz Golaszewski <brgl@...ev.pl> 於 2019年3月27日 週三 下午9:08寫道：
> >
> > śr., 27 mar 2019 o 11:17 Axel Lin <axel.lin@...ics.com> napisał(a):
> > >
> > > > Hi,
> > > >
> > > > what tree is this patch based on, because it doesn't apply on top of 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 way.
> I don't have public git tree for linux-kernel.
> I think you should try linux-next tree, this patch can be applied to linux-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