public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Benson Leung <bleung@google.com>,
	Prashant Malani <pmalani@chromium.org>,
	Jameson Thies <jthies@google.com>,
	"Regupathy, Rajaram" <rajaram.regupathy@intel.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Won Chung <wonchung@google.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] usb: typec: Separate USB Power Delivery from USB Type-C
Date: Wed, 27 Apr 2022 14:16:48 +0300	[thread overview]
Message-ID: <YmkmILWlbvoZaXKZ@kuha.fi.intel.com> (raw)
In-Reply-To: <YmkD2/r1imDT5qTz@kroah.com>

On Wed, Apr 27, 2022 at 10:50:35AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 27, 2022 at 11:17:49AM +0300, Heikki Krogerus wrote:
> > On Wed, Apr 27, 2022 at 09:30:30AM +0200, Greg Kroah-Hartman wrote:
> > > > > "struct pd" is just about the shortest structure name I've seen in the
> > > > > kernel so far.  How about using some more letters?  :)
> > > > 
> > > > Okay, I'll make it usbpd.
> > > 
> > > How about some more vowels: "struct usb_power_delivery" please.  This
> > > isn't the 1980's :)
> > 
> > "struct usb_power_delivery" is fine, but I would still really really
> > want to use "struct usbpd_capabilities" instead of
> > "struct usb_power_delivery_capabilities" - it's just too long.
> > Is that okay?
> 
> Nah, spell it out please, we don't use "usbpd" anywhere, and again, we
> don't have a limit of characters.  Most editors should auto-complete
> anyway :)

Very well.

> > > > > The kobject question above goes to the code as well.  You are creating a
> > > > > bunch of raw kobjects still, why?  This should all fit into the driver
> > > > > model and kobjects shouldn't be needed.  Are you trying to nest too deep
> > > > > in the attributes?  If so, kobjects will not work as userspace tools
> > > > > will not realize they are there and are attributes at all.
> > > > 
> > > > They are not raw kobjects, they are all devices now. That header just
> > > > needs to be fixed.
> > > 
> > > You have loads of kobject attributes in the .c file.  Either I read it
> > > wrong, or you are doing something wrong, as that should never be the
> > > case for a driver or device.
> > 
> > Hmm, I'm probable still doing something wrong...
> 
> All of your sysfs callbacks should have a struct device, not a kobject.
> You might just be getting lucky in that we are casting around a pointer
> of the correct layout.  But the compiler should have caught that
> somewhere, please look into it.

I'll fix this.

thanks,

-- 
heikki

  reply	other threads:[~2022-04-27 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 12:49 [PATCH v3 0/3] usb: typec: Separate USB PD from USB Type-C Heikki Krogerus
2022-04-25 12:49 ` [PATCH v3 1/3] usb: typec: Separate USB Power Delivery " Heikki Krogerus
2022-04-26 12:07   ` Greg Kroah-Hartman
2022-04-27  6:42     ` Heikki Krogerus
2022-04-27  7:30       ` Greg Kroah-Hartman
2022-04-27  8:17         ` Heikki Krogerus
2022-04-27  8:50           ` Greg Kroah-Hartman
2022-04-27 11:16             ` Heikki Krogerus [this message]
2022-04-25 12:49 ` [PATCH v3 2/3] usb: typec: USB Power Deliver helpers for ports and partners Heikki Krogerus
2022-04-25 12:49 ` [PATCH v3 3/3] usb: typec: tcpm: Register USB Power Delivery Capabilities Heikki Krogerus

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=YmkmILWlbvoZaXKZ@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=bleung@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jthies@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=pmalani@chromium.org \
    --cc=rajaram.regupathy@intel.com \
    --cc=wonchung@google.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