From: Vinod Koul <vinod.koul@intel.com>
To: Alexander Kochetkov <al.kochet@gmail.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: pl330: fix descriptor allocation fail
Date: Thu, 28 Sep 2017 13:17:50 +0530 [thread overview]
Message-ID: <20170928074750.GZ30097@localhost> (raw)
In-Reply-To: <CD7EEDA0-AF93-47AB-8929-141BB335F3C8@gmail.com>
On Tue, Sep 26, 2017 at 09:03:50PM +0300, Alexander Kochetkov wrote:
> Hello Vinod! Thanks for review!
>
> > 26 сент. 2017 г., в 20:37, Vinod Koul <vinod.koul@intel.com> написал(а):
> >
> > Tested-by please...
>
> In order to test the patch the driver should be rebuild with NR_DEFAULT_DESC defined to 1
> and with some trace code included. Is it OK if I provide second patch I used for testing
> with trace showing how change work?
>
> > one more wrapper why, we dont have any logic here!
> The idea was to keep rest of driver code intact. Ok, I’ll send v2 with no wrappers.
>
> > right justifed please
>
>
> Some functions has two tabs on second line, some has alignment to beginning of
> argument declaration. How correct?
>
> 1) or like this (two tabs)
> static int add_desc(struct list_head *pool, spinlock_t *lock,
> gfp_t flg, int count)
>
> 2) Like this:
> static int add_desc(struct list_head *pool, spinlock_t *lock,
> gfp_t flg, int count)
Second one with one more tab :)
See Section 2 Breaking long lines and strings in
Documentation/process/coding-style.rst
--
~Vinod
prev parent reply other threads:[~2017-09-28 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 10:00 [PATCH] dmaengine: pl330: fix descriptor allocation fail Alexander Kochetkov
2017-09-26 17:37 ` Vinod Koul
2017-09-26 18:03 ` Alexander Kochetkov
2017-09-28 7:47 ` 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=20170928074750.GZ30097@localhost \
--to=vinod.koul@intel.com \
--cc=al.kochet@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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