From: Vinod Koul <vkoul@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: linux-kernel@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
dmaengine@vger.kernel.org
Subject: [next,v2,1/2] dmaengine: bcm-sba-raid: Use dev_get_drvdata()
Date: Mon, 29 Apr 2019 10:47:36 +0530 [thread overview]
Message-ID: <20190429051736.GE3845@vkoul-mobl.Dlink> (raw)
On 28-04-19, 12:00, Kefeng Wang wrote:
> Using dev_get_drvdata directly.
>
Applied both, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: linux-kernel@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH next v2 1/2] dmaengine: bcm-sba-raid: Use dev_get_drvdata()
Date: Mon, 29 Apr 2019 10:47:36 +0530 [thread overview]
Message-ID: <20190429051736.GE3845@vkoul-mobl.Dlink> (raw)
Message-ID: <20190429051736.WIkuqaX92OC-09afD6OMz1iKSeL1Le53gUQmULawbr4@z> (raw)
In-Reply-To: <20190428040025.142181-1-wangkefeng.wang@huawei.com>
On 28-04-19, 12:00, Kefeng Wang wrote:
> Using dev_get_drvdata directly.
>
Applied both, thanks
--
~Vinod
next prev reply other threads:[~2019-04-29 5:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190423075020.173734-1-wangkefeng.wang@huawei.com>
2019-04-23 7:49 ` [next,03/25] dmaengine: Use dev_get_drvdata() Kefeng Wang
2019-04-23 7:49 ` [PATCH next 03/25] " Kefeng Wang
2019-04-26 11:52 ` [next,03/25] " Vinod Koul
2019-04-26 11:52 ` [PATCH next 03/25] " Vinod Koul
2019-04-28 4:00 ` [next,v2,1/2] dmaengine: bcm-sba-raid: " Kefeng Wang
2019-04-28 4:00 ` [PATCH next v2 1/2] " Kefeng Wang
2019-04-28 4:00 ` [next,v2,2/2] dmaengine: nbpfaxi: " Kefeng Wang
2019-04-28 4:00 ` [PATCH next v2 2/2] " Kefeng Wang
2019-04-29 5:17 ` Vinod Koul [this message]
2019-04-29 5:17 ` [PATCH next v2 1/2] dmaengine: bcm-sba-raid: " Vinod Koul
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=20190429051736.GE3845@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=wangkefeng.wang@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