From: nick <xerofoify@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: khalasa@piap.pl, bigeasy@linutronix.de, paulmcquad@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm:Change unlabeled block of code to a else block in the function dma_pool_free
Date: Tue, 07 Jul 2015 18:51:47 -0400 [thread overview]
Message-ID: <559C5803.50007@gmail.com> (raw)
In-Reply-To: <20150707154106.cd2f4e024a11c02993f02298@linux-foundation.org>
On 2015-07-07 06:41 PM, Andrew Morton wrote:
> On Mon, 6 Jul 2015 19:30:31 -0400 Nicholas Krause <xerofoify@gmail.com> wrote:
>
>> This fixes the unlabeled block of code after the if statement that
>> executes if the passed dma variable of type dma_addr_t minus the
>> structure pointer page's dma member is equal to the variable offset
>> into a else block as this block should run when the if statement check
>>
>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
>> ---
>> mm/dmapool.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/mm/dmapool.c b/mm/dmapool.c
>> index fd5fe43..ce7ff4b 100644
>> --- a/mm/dmapool.c
>> +++ b/mm/dmapool.c
>> @@ -434,8 +434,7 @@ void dma_pool_free(struct dma_pool *pool, void *vaddr, dma_addr_t dma)
>> "dma_pool_free %s, %p (bad vaddr)/%Lx\n",
>> pool->name, vaddr, (unsigned long long)dma);
>> return;
>> - }
>> - {
>> + } else {
>> unsigned int chain = page->offset;
>> while (chain < pool->allocation) {
>> if (chain != offset) {
>
> This patch has no effect?
>
It's a cleanup as clearly people didn't make this into a if/else statement block as clearly this
needs to run if the if statement fails and making into a else block makes this easier to understand
them a unnamed block. If you prefer we can just remove the brackets creating this block otherwise
that's my reasoning.
Nick
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-07-07 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 23:30 Nicholas Krause
2015-07-07 22:41 ` Andrew Morton
2015-07-07 22:51 ` nick [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=559C5803.50007@gmail.com \
--to=xerofoify@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=khalasa@piap.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmcquad@gmail.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