From: Aaron Sierra <asierra@xes-inc.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "Agócs Pál" <agocs.pal.86@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] lpc_ich: fix gpio base and control offsets
Date: Mon, 04 Feb 2013 09:38:15 -0600 (CST) [thread overview]
Message-ID: <c9391ccb-e37a-4f3d-b71d-44e6a046a490@zimbra> (raw)
In-Reply-To: <20130203170213.GQ8476@sortiz-mobl>
> On Thu, Jan 24, 2013 at 02:52:39PM -0600, Aaron Sierra wrote:
> > In ICH5 and earlier the GPIOBASE and GPIOCTRL registers are found
> > at
> > offsets 0x58 and 0x5C, respectively. This patch allows GPIO access
> > to
> > properly be enabled (and disabled) for these chipsets.
> >
> > Signed-off-by: Agócs Pál <agocs.pal.86@gmail.com>
> > Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
> > ---
> > drivers/mfd/lpc_ich.c | 109
> > ++++++++++++++++++++++++++++++++++---------------
> > 1 file changed, 76 insertions(+), 33 deletions(-)
> I applied this one to my for-next branch, but:
>
>
> > @@ -858,14 +874,35 @@ wdt_done:
> > static int lpc_ich_probe(struct pci_dev *dev,
> > const struct pci_device_id *id)
> > {
> > + struct lpc_ich_priv *priv;
> > int ret;
> > bool cell_added = false;
> >
> > - ret = lpc_ich_init_wdt(dev, id);
> > + priv = kmalloc(GFP_KERNEL, sizeof(struct lpc_ich_priv));
> > + if (!priv)
> > + return -ENOMEM;
> Could you please come back to me with a follow up patch that would
> convert this to the devm_kzalloc() API ?
Yeah, no problem.
-Aaron S.
next prev parent reply other threads:[~2013-02-04 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b9fec05c-d383-4282-b2af-c95855ff6abb@zimbra>
2013-01-24 20:52 ` Aaron Sierra
2013-01-25 9:47 ` Linus Walleij
2013-01-25 10:04 ` Paul Bolle
2013-01-25 11:06 ` Linus Walleij
2013-01-25 12:00 ` Paul Bolle
2013-01-25 12:43 ` Linus Walleij
2013-01-25 13:25 ` Paul Bolle
2013-01-25 13:42 ` Paul Bolle
2013-01-25 15:22 ` Aaron Sierra
2013-01-28 11:41 ` Paul Bolle
2013-01-25 13:44 ` Peter Hurley
2013-01-25 15:28 ` Peter Hurley
2013-01-25 16:48 ` Samuel Ortiz
2013-01-28 10:11 ` Linus Walleij
2013-01-28 11:45 ` Paul Bolle
2013-02-03 17:02 ` Samuel Ortiz
2013-02-04 15:38 ` Aaron Sierra [this message]
2013-02-14 22:48 ` Anatol Pomozov
2013-02-15 10:16 ` Samuel Ortiz
2013-02-15 14:28 ` Anatol Pomozov
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=c9391ccb-e37a-4f3d-b71d-44e6a046a490@zimbra \
--to=asierra@xes-inc.com \
--cc=agocs.pal.86@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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®