From: Chanwoo Choi <cwchoi00@gmail.com>
To: Bumwoo Lee <bw365.lee@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Simplify extcon_dev_register function.
Date: Tue, 21 Mar 2023 05:33:29 +0900 [thread overview]
Message-ID: <e4285e0b-32a3-a12b-3d99-1846b79c2607@gmail.com> (raw)
In-Reply-To: <20230320031939.28862-1-bw365.lee@samsung.com>
On 23. 3. 20. 12:19, Bumwoo Lee wrote:
> It was modified to increase readability.
>
> Changes from v4:
> added null checking of edev on each function.
>
> Chages from v3:
> removed possibility of kfree(NULL).
>
> Chages from v2:
> resolved possible memory leak of dev->cables.
>
> Changes from v1:
> added return value handling.
>
> Bumwoo Lee (3):
> extcon: Add extcon_alloc_cables to simplify extcon register function
> extcon: Add extcon_alloc_muex to simplify extcon register function
> extcon: Add extcon_alloc_groups to simplify extcon register function
>
> drivers/extcon/extcon.c | 281 +++++++++++++++++++++++-----------------
> 1 file changed, 165 insertions(+), 116 deletions(-)
>
Applied them. Thanks.
--
Best Regards,
Samsung Electronics
Chanwoo Choi
prev parent reply other threads:[~2023-03-20 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230320031947epcas1p1aa5b69c95a6f00400ca6cc78a5ddd17b@epcas1p1.samsung.com>
2023-03-20 3:19 ` Bumwoo Lee
[not found] ` <CGME20230320031947epcas1p370cac9b65ba7267554e3c342a858bb43@epcas1p3.samsung.com>
2023-03-20 3:19 ` [PATCH v5 1/3] extcon: Add extcon_alloc_cables to simplify extcon register function Bumwoo Lee
[not found] ` <CGME20230320031947epcas1p4e2a38d0d56cec1bca48e46e1130fe8db@epcas1p4.samsung.com>
2023-03-20 3:19 ` [PATCH v5 2/3] extcon: Add extcon_alloc_muex " Bumwoo Lee
[not found] ` <CGME20230320031947epcas1p17117b8bc458903348e9b29061d00b343@epcas1p1.samsung.com>
2023-03-20 3:19 ` [PATCH v5 3/3] extcon: Add extcon_alloc_groups " Bumwoo Lee
2023-03-20 20:33 ` 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=e4285e0b-32a3-a12b-3d99-1846b79c2607@gmail.com \
--to=cwchoi00@gmail.com \
--cc=bw365.lee@samsung.com \
--cc=cw00.choi@samsung.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®