From: Chanwoo Choi <cw00.choi@samsung.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] extcon: deduplicate code in extcon_set_state_sync()
Date: Thu, 16 Dec 2021 12:05:18 +0900 [thread overview]
Message-ID: <09ea6f93-4aae-1f74-bb54-0453908a7102@samsung.com> (raw)
In-Reply-To: <20211123145301.778629-1-alexander.stein@ew.tq-group.com>
On 11/23/21 11:53 PM, Alexander Stein wrote:
> Finding the cable index and checking for changed status is also done
> in extcon_set_state(). So calling extcon_set_state_sync() will do these
> checks twice. Remove them and use these checks from extcon_set_state().
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> I noticed this duplicated code while debugging an extcon related issue.
> I do not know if it is allowed in the kernel to assume some behavior in
> EXPORT_SYMBOL* functions, but as the two functions mentioned are in the
> same source file it should be ok.
> In the case it is not okay to assume some behaviour,
> extcon_set_state_sync() is missing a check for !edev, like
> extcon_set_state() does.
>
> drivers/extcon/extcon.c | 14 +-------------
> 1 file changed, 1 insertion(+), 13 deletions(-)
>
> diff --git a/drivers/extcon/extcon.c b/drivers/extcon/extcon.c
> index e7a9561a826d..a09e704fd0fa 100644
> --- a/drivers/extcon/extcon.c
> +++ b/drivers/extcon/extcon.c
> @@ -576,19 +576,7 @@ EXPORT_SYMBOL_GPL(extcon_set_state);
> */
> int extcon_set_state_sync(struct extcon_dev *edev, unsigned int id, bool state)
> {
> - int ret, index;
> - unsigned long flags;
> -
> - index = find_cable_index_by_id(edev, id);
> - if (index < 0)
> - return index;
> -
> - /* Check whether the external connector's state is changed. */
> - spin_lock_irqsave(&edev->lock, flags);
> - ret = is_extcon_changed(edev, index, state);
> - spin_unlock_irqrestore(&edev->lock, flags);
> - if (!ret)
> - return 0;
> + int ret;
>
> ret = extcon_set_state(edev, id, state);
> if (ret < 0)
>
Applied it. Thanks.
--
Best Regards,
Chanwoo Choi
Samsung Electronics
prev parent reply other threads:[~2021-12-16 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211123145318epcas1p17f6567ed89ec7f8f3ab3c007c58b1fe0@epcas1p1.samsung.com>
2021-11-23 14:53 ` Alexander Stein
2021-12-16 3:05 ` Chanwoo Choi [this message]
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=09ea6f93-4aae-1f74-bb54-0453908a7102@samsung.com \
--to=cw00.choi@samsung.com \
--cc=alexander.stein@ew.tq-group.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
all inboxes | Powered by JetHome®