From: Akira shimahara <akira215corp@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, greg@kroah.com
Cc: zbr@ioremap.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/9] w1_therm: adding code comments and code reordering
Date: Sun, 10 May 2020 10:54:52 +0200 [thread overview]
Message-ID: <fab87953187dd8b2c9d2bc6f8ea4f1e8042a8ac0.camel@gmail.com> (raw)
In-Reply-To: <eb73984b-8317-a0e9-90ed-2956d3fbc6b0@infradead.org>
Le samedi 09 mai 2020 à 19:26 -0700, Randy Dunlap a écrit :
> > +
> > +/*----------------------------------Structs-----------------------
> > ----------*/
> > +
> > +/**
> > + * struct w1_therm_family_converter
> > + * \brief Used to bind standard function call
> > + * to device specific function
> > + * it could be routed to NULL if device don't support feature
> > + */
>
>
> Hi,
>
>
>
> All of the struct and function documentation comments in all patches
> in
>
> this patch series should be using kernel-doc notation instead of the
> above
>
> (whatever it is; I don't know what it is).
>
>
>
>
>
> > +struct w1_therm_family_converter {
> > + u8 broken;
> > + u16 reserved;
> > + struct w1_family *f;
> > + int (*convert)(u8 rom[9]);
> > + int (*precision)(struct device *device, int val);
> > + int (*eeprom)(struct device *device);
> > +};
> > +
>
>
> thanks.
>
> --
>
> ~Randy
Hi,
Well noted, I will do it and re submit the serie. Thanks for your time.
Akira SHIMAHARA
prev parent reply other threads:[~2020-05-10 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 23:57 Akira Shimahara
2020-05-10 2:26 ` Randy Dunlap
2020-05-10 8:54 ` Akira shimahara [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=fab87953187dd8b2c9d2bc6f8ea4f1e8042a8ac0.camel@gmail.com \
--to=akira215corp@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=zbr@ioremap.net \
/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®