mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Kamil Konieczny <k.konieczny@partner.samsung.com>
Cc: "Tobin C. Harding" <me@tobin.cc>,
	"David S. Miller" <davem@davemloft.net>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: clear htmldocs build warnings for crypto/hash
Date: Tue, 9 Jan 2018 02:56:19 +1100	[thread overview]
Message-ID: <20180108155619.GA5350@gondor.apana.org.au> (raw)
In-Reply-To: <724b85c9-f3df-15b2-7aa2-4089f232c155@partner.samsung.com>

On Mon, Jan 08, 2018 at 02:11:21PM +0100, Kamil Konieczny wrote:
> 
> 
> On 07.01.2018 00:01, Tobin C. Harding wrote:
> > SPHINX build emits multiple warnings of kind:
> > 
> > 	warning: duplicate section name 'Note'
> > 
> > (when building kernel via make target 'htmldocs')
> > 
> > This is caused by repeated use of comments of form:
> > 
> > 	* Note: soau soaeusoa uoe
> > 
> > We can change the format without loss of clarity and clear the build
> > warnings.
> > 
> > Add '**[mandatory]**' or '**[optional]**' as kernel-doc field element
> > description prefix
> > 
> > This renders in HTML as (prefixes in bold)
> > 
> > final
> >     [mandatory] Retrieve result from the driver. This function finalizes the
> >     transformation and retrieves the resulting hash from the driver and
> >     pushes it back to upper layers. No data processing happens at this
> >     point unless hardware requires it to finish the transformation (then
> >     the data buffered by the device driver is processed).
> > 
> > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> > ---
> > 
> > This patch begs the question why the other members of struct ahash_alg
> > are not marked? Some are marked 'optional' some 'mandatory'. It would
> > seem that if the marking were necessary for some members it is necessary
> > for all to eliminate ambiguity?
> > 
> > thanks
> 
> import, export are optional

No import/export must be implemented for all hashes.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2018-01-08 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180106230157epcas2p2a3dc70ac85fbd7861ddf916fde5dd2be@epcas2p2.samsung.com>
2018-01-06 23:01 ` Tobin C. Harding
2018-01-08 13:11   ` Kamil Konieczny
2018-01-08 15:56     ` Herbert Xu [this message]
2018-01-08 16:43       ` Kamil Konieczny
2018-01-09  7:41         ` Herbert Xu
2018-01-12 12:26   ` Herbert Xu

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=20180108155619.GA5350@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=b.zolnierkie@samsung.com \
    --cc=davem@davemloft.net \
    --cc=k.konieczny@partner.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    /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®