mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Bryan Wu" <cooloney@kernel.org>, michael.hennerich@analog.com
Cc: akpm@linux-foundation.org,
	"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: + pcmcia-add-support-the-cf-pcmcia-driver-for-blackfin-try-2.patch added to -mm tree
Date: Wed, 21 May 2008 19:34:28 -0400	[thread overview]
Message-ID: <8bd0f97a0805211634r41cd2bafp94615fdfbdd4b7f7@mail.gmail.com> (raw)
In-Reply-To: <386072610805200051tcbf2d1bpcb981749c16879b6@mail.gmail.com>

On Tue, May 20, 2008 at 3:51 AM, Bryan Wu <cooloney@kernel.org> wrote:
> On Tue, May 20, 2008 at 2:08 PM,  <akpm@linux-foundation.org> wrote:
>> +config BFIN_CFPCMCIA
>> +       tristate "Blackfin CompactFlash PCMCIA Driver"
>> +       depends on PCMCIA && BLACKFIN
>> +       help
>> +         Say Y here to support the CompactFlash PCMCIA driver for Blackfin.

please add a common statement that tells you the module name if the
user builds it as a module.

>> + * author: Michael Hennerich (hennerich@blackfin.uclinux.org)

shouldnt this be MODULE_AUTHOR() ?

>> +       u_int irq;
>> +       u_short cd_pfx;

u_int forms are weird ... i'd wonder why we have these variations
anywhere in the kernel

>> +static int __init bfin_cf_probe(struct platform_device *pdev)

should be __devinit

>> +       cd_pfx = platform_get_irq(pdev, 1);     /*Card Detect GPIO PIN */
>> +       if (cd_pfx > MAX_BLACKFIN_GPIOS)
>> +               return -EINVAL;
>> +
>> +       if (gpio_request(cd_pfx, "pcmcia: CD")) {

i dont think that MAX_BLACKFIN_GPIOS check is needed.  the
gpio_request() function should already be doing it.

>> +               printk(KERN_ERR
>> +                      "BF5xx flash: Failed ro request Card Detect GPIO_%d\n",

"BF5xx flash" ?

>> +       cf = kzalloc(sizeof *cf, GFP_KERNEL);
>> +       if (!cf)
>> +               return -ENOMEM;

we dont call gpio_free() here or in the fail0 case below.
-mike

  parent reply	other threads:[~2008-05-21 23:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200805200608.m4K68d0N008092@imap1.linux-foundation.org>
2008-05-20  7:51 ` Bryan Wu
2008-05-20  8:02   ` Andrew Morton
2008-05-21  0:41     ` Mike Frysinger
2008-05-21 23:11       ` Andrew Morton
2008-05-21 23:23         ` Mike Frysinger
2008-05-21 23:34   ` Mike Frysinger [this message]
2008-05-27 11:15     ` Hennerich, Michael
2008-05-27 15:49       ` Bryan Wu

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=8bd0f97a0805211634r41cd2bafp94615fdfbdd4b7f7@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cooloney@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.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

all inboxes | Powered by JetHome®