public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Yu Kuai <yukuai3@huawei.com>
Cc: arnd@arndb.de, tudor.ambarus@microchip.com, yi.zhang@huawei.com,
	linux-kernel@vger.kernel.org, ludovic.desroches@microchip.com,
	dmaengine@vger.kernel.org, dan.j.williams@intel.com,
	plagnioj@jcrosoft.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 0/3] do exception handling appropriately in at_dma_xlate()
Date: Wed, 19 Aug 2020 09:59:25 +0530	[thread overview]
Message-ID: <20200819042925.GC2639@vkoul-mobl> (raw)
In-Reply-To: <20200817115728.1706719-1-yukuai3@huawei.com>

On 17-08-20, 19:57, Yu Kuai wrote:
> changes from V1:
> -separate different changes to different patches, as suggested by Vinod.

Please write proper cover letter explaining the patch series and also
the changes from v1..

I have applied the patches.

Thanks

> Yu Kuai (3):
>   dmaengine: at_hdmac: check return value of of_find_device_by_node() in
>     at_dma_xlate()
>   dmaengine: at_hdmac: add missing put_device() call in at_dma_xlate()
>   dmaengine: at_hdmac: add missing kfree() call in at_dma_xlate()
> 
>  drivers/dma/at_hdmac.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> -- 
> 2.25.4

-- 
~Vinod

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2020-08-19  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 11:57 [PATCH V2 0/3] do exception handling appropriately in at_dma_xlate() Yu Kuai
2020-08-17 11:57 ` [PATCH 1/3] dmaengine: at_hdmac: check return value of of_find_device_by_node() " Yu Kuai
2020-08-17 11:57 ` [PATCH 2/3] dmaengine: at_hdmac: add missing put_device() call " Yu Kuai
2020-08-17 11:57 ` [PATCH 3/3] dmaengine: at_hdmac: add missing kfree() " Yu Kuai
2020-08-19  4:29 ` 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=20200819042925.GC2639@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=tudor.ambarus@microchip.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox