The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Aaron Sierra <asierra@xes-inc.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: Sun, 3 Feb 2013 18:02:13 +0100	[thread overview]
Message-ID: <20130203170213.GQ8476@sortiz-mobl> (raw)
In-Reply-To: <3ffa5032-0565-48f0-a4ae-473452f4c902@zimbra>

Hi Arron,

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 ?

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  parent reply	other threads:[~2013-02-03 17:02 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 ` [PATCH v3] lpc_ich: fix gpio base and control offsets 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 [this message]
2013-02-04 15:38     ` Aaron Sierra
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=20130203170213.GQ8476@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=agocs.pal.86@gmail.com \
    --cc=asierra@xes-inc.com \
    --cc=linus.walleij@linaro.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