public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Johan Hovold <johan@kernel.org>, Oliver Neukum <oneukum@suse.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: drop misleading usb_set_intfdata() kernel doc
Date: Mon, 12 Dec 2022 15:04:50 +0100	[thread overview]
Message-ID: <b1a5874b-8028-db14-e2ac-ebe3967559a5@suse.com> (raw)
In-Reply-To: <Y5cvPulXceujfZv6@hovoldconsulting.com>



On 12.12.22 14:40, Johan Hovold wrote:
> On Mon, Dec 12, 2022 at 02:27:46PM +0100, Oliver Neukum wrote:
>> On 12.12.22 14:14, Johan Hovold wrote:
>>> On Mon, Dec 12, 2022 at 12:13:54PM +0100, Oliver Neukum wrote:
> 
>>> And in this case there was also no kernel doc for usb_get_intfdata()
>>> which is equally self documenting. Why add redundant docs for only one
>>> of these functions?
>>
>> Because knowing that one of them exists makes the other much more
>> obvious.
> 
> I doubt anyone finds out about this function by reading generated kernel
> documentation. You look at a driver, grep the function and look at the
> single-line implementation.

Look, we cannot solve the issue whether kerneldoc is a good idea
in general here. If you want to open that can of worms on lkml,
by all means. go for it.
But failing that, silently eliminating it is just not nice.

> But it was never perfectly good. It claims that a driver "should" use it,
> when it may not need to (think simple driver using devres) and talks

If you are presented with an interface something needs to be done
specific to that interface.

> about driver core resetting the pointer which is irrelevant.

But correct and topical. I am not arguing what people should or should
mot know.
  
If you just remove the last sentence, all will be well. And if you
insist replace "should" with "can".

	Regards
		Oliver


  reply	other threads:[~2022-12-12 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 12:06 [PATCH] USB: drop misleading usb_set_intfdata() kernel doc Johan Hovold
2022-12-12 10:19 ` Oliver Neukum
2022-12-12 10:31   ` Johan Hovold
2022-12-12 11:13     ` Oliver Neukum
2022-12-12 13:14       ` Johan Hovold
2022-12-12 13:27         ` Oliver Neukum
2022-12-12 13:40           ` Johan Hovold
2022-12-12 14:04             ` Oliver Neukum [this message]
2022-12-12 14:14               ` Johan Hovold
2022-12-12 15:25                 ` Alan Stern
2022-12-12 16:08                   ` Johan Hovold
2022-12-12 16:39                     ` Alan Stern

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=b1a5874b-8028-db14-e2ac-ebe3967559a5@suse.com \
    --to=oneukum@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    /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