mirror of
https://github.com/Fishwaldo/Star64_linux.git
synced 2025-03-16 12:14:06 +00:00
bnxt_en: fix kernel doc warnings in bnxt_hwrm.c
Parameter names in the comments did not match the function arguments.
Fixes: 2138081708
("bnxt_en: add support for HWRM request slices")
Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
Reported-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Michael Chan <michael.chan@broadcom.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Link: https://lore.kernel.org/r/20210901185315.57137-1-edwin.peer@broadcom.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
This commit is contained in:
parent
36e784a60b
commit
5240118f08
1 changed files with 7 additions and 7 deletions
|
@ -145,11 +145,11 @@ void hwrm_req_timeout(struct bnxt *bp, void *req, unsigned int timeout)
|
|||
* @bp: The driver context.
|
||||
* @req: The request for which calls to hwrm_req_dma_slice() will have altered
|
||||
* allocation flags.
|
||||
* @flags: A bitmask of GFP flags. These flags are passed to
|
||||
* dma_alloc_coherent() whenever it is used to allocate backing memory
|
||||
* for slices. Note that calls to hwrm_req_dma_slice() will not always
|
||||
* result in new allocations, however, memory suballocated from the
|
||||
* request buffer is already __GFP_ZERO.
|
||||
* @gfp: A bitmask of GFP flags. These flags are passed to dma_alloc_coherent()
|
||||
* whenever it is used to allocate backing memory for slices. Note that
|
||||
* calls to hwrm_req_dma_slice() will not always result in new allocations,
|
||||
* however, memory suballocated from the request buffer is already
|
||||
* __GFP_ZERO.
|
||||
*
|
||||
* Sets the GFP allocation flags associated with the request for subsequent
|
||||
* calls to hwrm_req_dma_slice(). This can be useful for specifying __GFP_ZERO
|
||||
|
@ -698,8 +698,8 @@ int hwrm_req_send_silent(struct bnxt *bp, void *req)
|
|||
* @bp: The driver context.
|
||||
* @req: The request for which indirect data will be associated.
|
||||
* @size: The size of the allocation.
|
||||
* @dma: The bus address associated with the allocation. The HWRM API has no
|
||||
* knowledge about the type of the request and so cannot infer how the
|
||||
* @dma_handle: The bus address associated with the allocation. The HWRM API has
|
||||
* no knowledge about the type of the request and so cannot infer how the
|
||||
* caller intends to use the indirect data. Thus, the caller is
|
||||
* responsible for configuring the request object appropriately to
|
||||
* point to the associated indirect memory. Note, DMA handle has the
|
||||
|
|
Loading…
Add table
Reference in a new issue