The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: Ben Nizette <bn@niasdigital.com>
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kernel <kernel@avr32linux.org>
Subject: Re: [PATCH] avr32: clean up mci platform code
Date: Fri, 18 Jul 2008 11:04:19 +0200	[thread overview]
Message-ID: <20080718110419.33581cd0@siona.local> (raw)
In-Reply-To: <1216363689.4004.80.camel@moss.renham>

On Fri, 18 Jul 2008 16:48:09 +1000
Ben Nizette <bn@niasdigital.com> wrote:

> This patch does a few small cleanups around the atmel mci platform code
> and in the atmel-mci driver.  The platform changes simply removes an
> unused variable, uses the fact that by the end we always have some form
> of platform data and notes that GPIO_PIN_NONE != 0.  This last point
> could cause the incorrect attempt to twice reserve pin PA0.

Indeed. The if (data) check is useless too since we make sure data
always points to something.

We should probably set the invalid pins to something like -EINVAL
eventually, but for now GPIO_PIN_NONE is consistent with everything
else around there.

> While we've got the hood up, add linux/err.h to the atmel-mci.c include
> list.  It needs it and generally pulls it by voodoo but I did once
> stumble across a config which don't build.

Yes, including linux/err.h is definitely the right thing to do.

> This is against Linus' latest git.
> 
> Signed-off-by: Ben Nizette <bn@niasdigital.com>

I've applied it to the avr32 tree since it touches mostly avr32 arch
code. Thanks a lot, Ben!

Haavard

      reply	other threads:[~2008-07-18  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  6:48 [PATCH] avr32: clean up mci platform code Ben Nizette
2008-07-18  9:04 ` Haavard Skinnemoen [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=20080718110419.33581cd0@siona.local \
    --to=haavard.skinnemoen@atmel.com \
    --cc=bn@niasdigital.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=kernel@avr32linux.org \
    --cc=linux-kernel@vger.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