public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [PATCH v2] mtd: nand: pxa3xx_nand: kill unused field 'drcmr_cmd'
Date: Mon, 07 Mar 2016 20:35:34 +0100	[thread overview]
Message-ID: <87pov6ulmh.fsf@belgarion.home> (raw)
In-Reply-To: <20160307183730.GU55664@google.com> (Brian Norris's message of "Mon, 7 Mar 2016 10:37:30 -0800")

Brian Norris <computersforpeace@gmail.com> writes:

> With this removal, we don't need to 'get' the second DMA resource
> either, as it's also unused.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
> On Sat, Mar 05, 2016 at 09:34:14AM +0100, Robert Jarzmik wrote:
>> Brian Norris <computersforpeace@gmail.com> writes:
>> > @@ -1812,7 +1811,6 @@ static int alloc_nand_resource(struct platform_device *pdev)
>> >  			ret = -ENXIO;
>> >  			goto fail_disable_clk;
>> >  		}
>> > -		info->drcmr_cmd = r->start;
>> >  	}
>> If you kill this field, why not kill also this block just above ?
>> 		r = platform_get_resource(pdev, IORESOURCE_DMA, 1);
>> 		if (r == NULL) {
>> 			dev_err(&pdev->dev,
>> 				"no resource defined for cmd DMA\n");
>> 			ret = -ENXIO;
>> 			goto fail_disable_clk;
>> 		}
>
> Indeed, why not.
>
>  drivers/mtd/nand/pxa3xx_nand.c | 10 ----------
>  1 file changed, 10 deletions(-)
Acked-by: Robert Jarzmik <robert.jarzmik@free.fr>

Cheers.

--
Robert

  reply	other threads:[~2016-03-07 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05  3:12 [PATCH] mtd: nand: pxa3xx_nand: kill unused field 'drcmr_cmd' Brian Norris
2016-03-05  8:34 ` Robert Jarzmik
2016-03-07 18:37   ` [PATCH v2] " Brian Norris
2016-03-07 19:35     ` Robert Jarzmik [this message]
2016-03-07 20:49       ` Brian Norris

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=87pov6ulmh.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=computersforpeace@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.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