All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liming Sun <lsun@mellanox.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andy@infradead.org>,
	Darren Hart <dvhart@infradead.org>,
	Vadim Pasternak <vadimp@mellanox.com>,
	David Woods <dwoods@mellanox.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] platform/mellanox: fix the mlx-bootctl sysfs
Date: Wed, 18 Dec 2019 15:26:23 +0000	[thread overview]
Message-ID: <DB6PR05MB3223ED6CFF01AE972F608B6EA1530@DB6PR05MB3223.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CAHp75VfVL8fs_VXQgL85QPnW2N+zsLq4dWYkhs3xdMAjcfRgTg@mail.gmail.com>

Thanks Andy for the comments. v3 has been posted with the updates.

- Liming

> -----Original Message-----
> From: Andy Shevchenko <andy.shevchenko@gmail.com>
> Sent: Wednesday, December 18, 2019 8:01 AM
> To: Liming Sun <lsun@mellanox.com>
> Cc: Andy Shevchenko <andy@infradead.org>; Darren Hart <dvhart@infradead.org>; Vadim Pasternak <vadimp@mellanox.com>; David
> Woods <dwoods@mellanox.com>; Platform Driver <platform-driver-x86@vger.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@vger.kernel.org>
> Subject: Re: [PATCH v2] platform/mellanox: fix the mlx-bootctl sysfs
> 
> On Fri, Dec 13, 2019 at 5:21 PM Liming Sun <lsun@mellanox.com> wrote:
> 
> > +       ret = sysfs_create_group(&dev->kobj, &mlxbf_bootctl_group);
> > +       if (ret) {
> > +               dev_err(dev, "failed to create attributes, err=%d\n", ret);
> > +               return ret;
> > +       }
> > +
> >         /* Ensure we have the UUID we expect for this service. */
> >         arm_smccc_smc(MLXBF_BOOTCTL_SIP_SVC_UID, 0, 0, 0, 0, 0, 0, 0, &res);
> >         guid_parse(mlxbf_bootctl_svc_uuid_str, &guid);
> > @@ -305,8 +312,16 @@ static int mlxbf_bootctl_probe(struct platform_device *pdev)
> >         return 0;
> >  }
> >
> > +static int mlxbf_bootctl_remove(struct platform_device *pdev)
> > +{
> > +       sysfs_remove_group(&pdev->dev.kobj, &mlxbf_bootctl_group);
> > +
> > +       return 0;
> > +}
> > +
> >  static struct platform_driver mlxbf_bootctl_driver = {
> >         .probe = mlxbf_bootctl_probe,
> > +       .remove = mlxbf_bootctl_remove,
> >         .driver = {
> >                 .name = "mlxbf-bootctl",
> >                 .groups = mlxbf_bootctl_groups,
> 
> Please, use dev_groups member of the struct driver instead of above approach.
> 
> --
> With Best Regards,
> Andy Shevchenko

  reply	other threads:[~2019-12-18 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 19:23 [PATCH v1 1/1] platform/mellanox: fix the mlx-bootctl sysfs Liming Sun
2019-12-13 10:21 ` Andy Shevchenko
2019-12-13 15:22   ` Liming Sun
2019-12-13 15:21 ` [PATCH v2] " Liming Sun
2019-12-18 13:00   ` Andy Shevchenko
2019-12-18 15:26     ` Liming Sun [this message]
2019-12-18 15:24 ` [PATCH v3] " Liming Sun
2019-12-18 17:59   ` Andy Shevchenko
2019-12-18 18:36     ` Liming Sun
2019-12-18 18:35 ` [PATCH v4] " Liming Sun

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=DB6PR05MB3223ED6CFF01AE972F608B6EA1530@DB6PR05MB3223.eurprd05.prod.outlook.com \
    --to=lsun@mellanox.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=dwoods@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=vadimp@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.