linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend] extcon: Fix attached value returned by is_extcon_changed
Date: Mon, 21 Sep 2015 13:29:35 +0200	[thread overview]
Message-ID: <55FFEA1F.7050500@redhat.com> (raw)
In-Reply-To: <55FF5F2F.9010504@samsung.com>

Hi,

On 21-09-15 03:36, Chanwoo Choi wrote:
> On 2015? 09? 20? 21:34, Hans de Goede wrote:
>> is_extcon_changed should only check the idx-th bit of new, not
>> the entirety of new when setting attached.
>>
>> This fixes extcon sending notifications that a cable was inserted when
>> it gets removed while another cable is still connected.
>>
>> Cc: stable at vger.kernel.org
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>>   drivers/extcon/extcon.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/extcon/extcon.c b/drivers/extcon/extcon.c
>> index a07addd..8dd0af1 100644
>> --- a/drivers/extcon/extcon.c
>> +++ b/drivers/extcon/extcon.c
>> @@ -159,7 +159,7 @@ static int find_cable_index_by_name(struct extcon_dev *edev, const char *name)
>>   static bool is_extcon_changed(u32 prev, u32 new, int idx, bool *attached)
>>   {
>>   	if (((prev >> idx) & 0x1) != ((new >> idx) & 0x1)) {
>> -		*attached = new ? true : false;
>> +		*attached = ((new >> idx) & 0x1) ? true : false;
>>   		return true;
>>   	}
>>
>>
>
> This patch was already applied[1].
> [1] https://git.kernel.org/cgit/linux/kernel/git/chanwoo/extcon.git/log/?h=extcon-next

Yet it is not in 4.3-rc1, applying the patch to your tree is not useful
unless you also send a pull-req to get the changes in your tree actually
merged ...

Regards,

Hans

  reply	other threads:[~2015-09-21 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 12:34 [PATCH resend] extcon: Fix attached value returned by is_extcon_changed Hans de Goede
2015-09-20 12:34 ` Hans de Goede
2015-09-21  1:36   ` Chanwoo Choi
2015-09-21 11:29     ` Hans de Goede [this message]
2015-09-22  1:44       ` Chanwoo Choi
2015-09-22  7:12         ` Hans de Goede
2015-09-22  7:54           ` Chanwoo Choi

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=55FFEA1F.7050500@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).