From: Chanwoo Choi <cw00.choi@samsung.com>
To: Hans de Goede <hdegoede@redhat.com>, linux-kernel@vger.kernel.org
Cc: chanwoo@kernel.org, myungjoo.ham@samsung.com
Subject: Re: [PATCH 2/2] extcon: Add new extcon_register_notifier_all() to monitor all external connectors
Date: Tue, 04 Apr 2017 19:52:39 +0900 [thread overview]
Message-ID: <58E37AF7.6050705@samsung.com> (raw)
In-Reply-To: <18cb3d7a-6e75-c9a4-e4a8-604d8538cd49@redhat.com>
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 <hdegoede@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
next prev parent reply other threads:[~2017-04-04 10:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170330083943epcas1p4ccc3a12576a7232162a682b73eaeea0b@epcas1p4.samsung.com>
2017-03-30 8:39 ` [PATCH 1/2] extcon: Use BIT() macro for the left-shift operation Chanwoo Choi
2017-03-30 8:39 ` [PATCH 2/2] extcon: Add new extcon_register_notifier_all() to monitor all external connectors Chanwoo Choi
2017-03-30 9:04 ` Hans de Goede
2017-03-30 9:20 ` Chanwoo Choi
2017-03-30 14:58 ` Hans de Goede
2017-04-03 7:24 ` Chanwoo Choi
2017-04-03 11:14 ` Hans de Goede
2017-04-04 4:53 ` Chanwoo Choi
2017-04-04 10:47 ` Hans de Goede
2017-04-04 10:52 ` Chanwoo Choi [this message]
2017-03-30 9:05 ` Andy Shevchenko
2017-03-30 9:24 ` Chanwoo Choi
2017-03-30 10:42 ` Andy Shevchenko
2017-03-30 10:56 ` Chanwoo Choi
2017-03-30 11:09 ` Andy Shevchenko
2017-03-30 8:59 ` [PATCH 1/2] extcon: Use BIT() macro for the left-shift operation Andy Shevchenko
2017-03-30 9:15 ` Chanwoo Choi
2017-03-30 10:38 ` Andy Shevchenko
2017-03-30 10:52 ` Chanwoo Choi
2017-03-30 11:12 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58E37AF7.6050705@samsung.com \
--to=cw00.choi@samsung.com \
--cc=chanwoo@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).