From: maowenan <maowenan@huawei.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: <dan.j.williams@intel.com>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH v2 linux-next 0/2] change mux_configure32() to static
Date: Tue, 20 Aug 2019 19:48:48 +0800 [thread overview]
Message-ID: <bdd606cb-535f-c153-d51f-4571db2d23dc@huawei.com> (raw)
In-Reply-To: <20190820114105.GW12733@vkoul-mobl.Dlink>
On 2019/8/20 19:41, Vinod Koul wrote:
> On 14-08-19, 15:21, Mao Wenan wrote:
>> First patch is to make mux_configure32() static to avoid sparse warning,
>> the second patch is to chage alignment of two functions.
>
> The subsystem name is "dmaengine" please use that in future, I have
> fixed that and applied
Okay, thanks.
>
>> v2: change subject from "drivers: dma: Fix sparse warning for mux_configure32"
>> to "drivers: dma: make mux_configure32 static", and cleanup the log. And add
>> one patch to change alignment of two functions.
>>
>> Mao Wenan (2):
>> drivers: dma: make mux_configure32 static
>> drivers: dma: change alignment of mux_configure32 and
>> fsl_edma_chan_mux
>>
>> drivers/dma/fsl-edma-common.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> --
>> 2.20.1
>
prev parent reply other threads:[~2019-08-20 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 7:21 [PATCH v2 linux-next 0/2] change mux_configure32() to static Mao Wenan
2019-08-14 7:21 ` [PATCH v2 linux-next 1/2] drivers: dma: make mux_configure32 static Mao Wenan
2019-08-14 7:21 ` [PATCH v2 linux-next 2/2] drivers: dma: change alignment of mux_configure32 and fsl_edma_chan_mux Mao Wenan
2019-08-20 11:41 ` [PATCH v2 linux-next 0/2] change mux_configure32() to static Vinod Koul
2019-08-20 11:48 ` maowenan [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=bdd606cb-535f-c153-d51f-4571db2d23dc@huawei.com \
--to=maowenan@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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).