From: Daniel Campello <campello@chromium.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Wei Yongjun <weiyongjun1@huawei.com>,
Duncan Laurie <dlaurie@google.com>,
Nick Crews <ncrews@chromium.org>,
Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH] platform/chrome: wilco_ec: Fix unregistration order
Date: Thu, 9 Jan 2020 10:30:51 -0700 [thread overview]
Message-ID: <20200109173051.GA78461@chromium.org> (raw)
In-Reply-To: <9cf68a0b-ed58-168a-4c04-753a7a9f55bd@collabora.com>
Hi Enric,
Thanks for helping get this in.
On Thu, Jan 09, 2020 at 10:06:37AM +0100, Enric Balletbo i Serra wrote:
> Hi Daniel,
>
> Many thanks for the patch, some comments below.
>
> On 8/1/20 17:35, Daniel Campello wrote:
> > Fixes the unregistration order on the Wilco EC core driver to follow the
> > christmas tree pattern.
> >
>
> It is logical to cleanup in remove's function in reverse order to probe, but
> that's not related to the Christmas tree pattern. I changed the commit
> description and queued for the autobuilders to play with. If all goes well will
> appear in chrome-platform-5.5
>
I got this confused. Thanks for pointing it out.
>
> > Signed-off-by: Daniel Campello <campello@chromium.org>
>
> Is this patch fixing an actual issue?
>
No issue, just style cleanup.
>
> Thanks,
> Enric
>
> > ---
> >
> > drivers/platform/chrome/wilco_ec/core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/platform/chrome/wilco_ec/core.c b/drivers/platform/chrome/wilco_ec/core.c
> > index 5210c357feefd4..2d5f027d8770f8 100644
> > --- a/drivers/platform/chrome/wilco_ec/core.c
> > +++ b/drivers/platform/chrome/wilco_ec/core.c
> > @@ -137,9 +137,9 @@ static int wilco_ec_remove(struct platform_device *pdev)
> > {
> > struct wilco_ec_device *ec = platform_get_drvdata(pdev);
> >
> > + platform_device_unregister(ec->telem_pdev);
> > platform_device_unregister(ec->charger_pdev);
> > wilco_ec_remove_sysfs(ec);
> > - platform_device_unregister(ec->telem_pdev);
> > platform_device_unregister(ec->rtc_pdev);
> > if (ec->debugfs_pdev)
> > platform_device_unregister(ec->debugfs_pdev);
> > --
> > 2.24.1.735.g03f4e72817-goog
> >
prev parent reply other threads:[~2020-01-09 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:35 [PATCH] platform/chrome: wilco_ec: Fix unregistration order Daniel Campello
2020-01-09 9:06 ` Enric Balletbo i Serra
2020-01-09 17:30 ` Daniel Campello [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=20200109173051.GA78461@chromium.org \
--to=campello@chromium.org \
--cc=bleung@chromium.org \
--cc=dlaurie@google.com \
--cc=enric.balletbo@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncrews@chromium.org \
--cc=weiyongjun1@huawei.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