dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dmaengine: Move kdoc description of struct dma_chan_percpu closer to it
Date: Mon, 31 May 2021 09:51:04 +0530	[thread overview]
Message-ID: <YLRkMJgGW3slzjWO@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20210518104323.37632-1-andriy.shevchenko@linux.intel.com>

On 18-05-21, 13:43, Andy Shevchenko wrote:
> We have split by unknown reason of kdoc and struct dma_chan_percpu definition.
> Join them back. No functional change.

Applied both, thanks

-- 
~Vinod

      parent reply	other threads:[~2021-05-31  4:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 10:43 [PATCH v1 1/2] dmaengine: Move kdoc description of struct dma_chan_percpu closer to it Andy Shevchenko
2021-05-18 10:43 ` [PATCH v1 2/2] dmaengine: hsu: Account transferred bytes Andy Shevchenko
2021-05-31  4:21 ` Vinod Koul [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=YLRkMJgGW3slzjWO@vkoul-mobl.Dlink \
    --to=vkoul@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).