Hi, On 2017년 04월 04일 19:47, Hans de Goede wrote: > Hi, > > On 03-04-17 13:14, Hans de Goede wrote: >> Hi, >> >> On 03-04-17 09:24, Chanwoo Choi wrote: > > <snip> > >>> As I already said, I think that extcon focus on sending the notification >>> to all of extcon consumers. >> >> Ok, then lets keep your patches as they are, I've added the patches >> from your extcon-test branch to my local repository, modified the drivers >> which I've pending upstream which need this to use the new functionality >> and tested things. >> >> Everything looks and works good with these patches, so please add my: >> >> Acked-and-Tested-by: Hans de Goede <hdego...@redhat.com> >> >> to them. >> >> It would be great if you can push these patches to extcon-next and >> then create a stable branch with these patches which other subsys >> maintainers can merge, so that I can start submitting patches which >> need this upstream (and also do a cleanup patch for the current axp288 >> charger code). > > I see that you've created a "ib-extcon-4.12" branch now, can I > refer other maintainers to that when submitting patches using > the new extcon_register_notifier_all(), or should I wait a bit ?
You need to wait for a few days before applying this patch on the extcon-next branch. After applying this patch on extcon-next, I'll send the pull request patch to both you and linux-kernel mailing list. And then you better to give the pull request mail to other subsystem maintainer. > > Regards, > > Hans > > > -- Best Regards, Chanwoo Choi Samsung Electronics
