[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZUWP5hOCLpVvOSfR3YNXF6HC4GaO5ptYify2_EPa=wOQ@mail.gmail.com>
Date: Thu, 6 May 2021 15:00:26 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: linux-mmc <linux-mmc@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Shawn Lin <shawn.lin@...k-chips.com>,
Avri Altman <avri.altman@....com>,
Masami Hiramatsu <masami.hiramatsu@...aro.org>,
linux-block <linux-block@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 06/11] mmc: core: Prepare mmc_send_cxd_data() to be
re-used for additional cmds
On Tue, May 4, 2021 at 6:12 PM Ulf Hansson <ulf.hansson@...aro.org> wrote:
> * NOTE: void *buf, caller for the buf is required to use DMA-capable
> * buffer or on-stack buffer (with some overhead in callee).
> */
> -static int
> -mmc_send_cxd_data(struct mmc_card *card, struct mmc_host *host,
> - u32 opcode, void *buf, unsigned len)
> +int mmc_send_adtc_data(struct mmc_card *card, struct mmc_host *host, u32 opcode,
> + u32 args, void *buf, unsigned len)
Just a note here (the change is good)
When applying please add some kerneldoc above mmc_send_adtc_data()
and expand the ADTC acronym and add some info explaining what it
is maybe a small protocol ref or so, so readers of the code get an
intuitive feeling for what this function does and what ADTC is.
Yours,
Linus Walleijq
Powered by blists - more mailing lists