linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vijaykumar@zilogic.com (Vijay Kumar B.)
To: linux-arm-kernel@lists.infradead.org
Subject: Contributing to PXA2xx pinctrl Driver
Date: Fri, 29 Jul 2016 15:14:22 +0530	[thread overview]
Message-ID: <579B2576.4020609@zilogic.com> (raw)
In-Reply-To: <20160729091932.GB1041@n2100.armlinux.org.uk>

On Friday 29 July 2016 02:49 PM, Russell King - ARM Linux wrote:
> On Fri, Jul 29, 2016 at 02:42:47PM +0530, Vijay Kumar B. wrote:
>> Hi Everyone,
>> I am looking at the pinctrl driver for drivers/pinctrl/pxa/pxa2xx.c. The
>> driver in mainline git and pxa2xx git (rjarzmik/linux on github) seems to
>> write to allocated memory rather than to registers.
> Please explain why you think that.
>

OK, I was wrong. I misread the purpose of the allocations done in the 
init() function. Sorry for the trouble.

Regards,
Vijay

      reply	other threads:[~2016-07-29  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  9:12 Contributing to PXA2xx pinctrl Driver Vijay Kumar B.
2016-07-29  9:19 ` Russell King - ARM Linux
2016-07-29  9:44   ` Vijay Kumar B. [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=579B2576.4020609@zilogic.com \
    --to=vijaykumar@zilogic.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).