From: Baruch Siach <baruch@tkos.co.il>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, dbrownell@users.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk, linux@arm.linux.org.uk
Subject: Re: [PATCH v6] gpio: driver for PrimeCell PL061 GPIO controller
Date: Fri, 19 Jun 2009 16:43:32 +0300 [thread overview]
Message-ID: <20090619134332.GG21428@tarshish> (raw)
In-Reply-To: <20090618151916.32d55e6e.akpm@linux-foundation.org>
Hi Andrew,
Thanks for your review.
On Thu, Jun 18, 2009 at 03:19:16PM -0700, Andrew Morton wrote:
> On Wed, 17 Jun 2009 09:34:37 +0300
> Baruch Siach <baruch@tkos.co.il> wrote:
> > ...
> >
> > +static int __init pl061_probe(struct amba_device *dev, struct amba_id *id)
> > +{
> > + struct pl061_platform_data *pdata;
> > + struct pl061_gpio *chip;
> > + struct list_head *chip_list;
> > + int ret, irq, i;
> > + static unsigned long init_irq[BITS_TO_LONGS(NR_IRQS)];
>
> We could perhaps use DECLARE_BITMAP() here. Which implies that the
> whole use of this bitmap should use the bitmap API rather than
> open-coded bitops.
>
> I don't know whether that would actually improve anything - it's just a
> thought..
I'll change that.
> > + if (!test_and_set_bit(irq, init_irq)) { /* list initialized? */
> > + chip_list = kmalloc(sizeof(*chip_list), GFP_KERNEL);
> > + if (chip_list == NULL) {
>
> We should do a clear_bit() here.
Will fix.
Should I post v7 of the entire patch, or just a fix-up for these issues?
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2009-06-19 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 6:34 [PATCH v6] gpio: driver for PrimeCell PL061 GPIO controller Baruch Siach
2009-06-18 22:19 ` Andrew Morton
2009-06-19 13:43 ` Baruch Siach [this message]
2009-06-21 6:14 ` Andrew Morton
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=20090619134332.GG21428@tarshish \
--to=baruch@tkos.co.il \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.