All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	linux-mmc@vger.kernel.org, Pavel Machek <pavel@denx.de>,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH 2/2] mmc: renesas_internal_dmac: Fix typo's
Date: Mon, 4 Apr 2022 20:21:55 +0200	[thread overview]
Message-ID: <Yks3Q75ZrUkXSjwz@ninjato> (raw)
In-Reply-To: <20220404172322.32578-3-prabhakar.mahadev-lad.rj@bp.renesas.com>

[-- Attachment #1: Type: text/plain, Size: 207 bytes --]


> -	/* This DMAC cannot handle if buffer is not 128-bytes alignment */
> +	/* This DMAC cannot handle if buffer is not 128-bytes aligned */

Well, as we are here now, I think this can be further improved.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-04-04 21:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 17:23 [PATCH 0/2] mmc: renesas: Trivial fixes Lad Prabhakar
2022-04-04 17:23 ` [PATCH 1/2] mmc: renesas_sdhi: Jump to error path instead of returning directly Lad Prabhakar
2022-04-04 18:02   ` Biju Das
2022-04-04 18:08     ` Lad, Prabhakar
2022-04-04 18:12       ` Biju Das
2022-04-05  3:51         ` Lad, Prabhakar
2022-04-07  7:13         ` Wolfram Sang
2022-04-04 17:23 ` [PATCH 2/2] mmc: renesas_internal_dmac: Fix typo's Lad Prabhakar
2022-04-04 18:21   ` Wolfram Sang [this message]
2022-04-05  3:50     ` Lad, Prabhakar
2022-04-05  4:45       ` Wolfram Sang
2022-04-05  5:13         ` Lad, Prabhakar
2022-04-05  7:18         ` Geert Uytterhoeven
2022-06-21 13:35 ` [PATCH 0/2] mmc: renesas: Trivial fixes Wolfram Sang
2022-06-21 14:03   ` Lad, Prabhakar

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=Yks3Q75ZrUkXSjwz@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=pavel@denx.de \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=ulf.hansson@linaro.org \
    --cc=yoshihiro.shimoda.uh@renesas.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.