mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanho Park <chanho61.park@samsung.com>
To: "'Linus Walleij'" <linus.walleij@linaro.org>
Cc: swarren@nvidia.com, Baohua.Song@csr.com,
	linux-kernel@vger.kernel.org,
	"'Kyungmin Park'" <kyungmin.park@samsung.com>
Subject: RE: [PATCH 1/2] pinctrl: correct a offset while enumerating pins
Date: Tue, 03 Jan 2012 17:37:39 +0900	[thread overview]
Message-ID: <008001ccc9f2$f38fadd0$daaf0970$%park@samsung.com> (raw)
In-Reply-To: <CACRpkdbnvZo4AN+yoeGwDaJ0yqOJT6VZO_9TmX4ZwdOCOE8Z5w@mail.gmail.com>

> -----Original Message-----
> From: Linus Walleij [mailto:linus.walleij@linaro.org]
> Sent: Tuesday, January 03, 2012 4:59 PM
> To: Chanho Park
> Cc: swarren@nvidia.com; Baohua.Song@csr.com; linux-
> kernel@vger.kernel.org; Kyungmin Park
> Subject: Re: [PATCH 1/2] pinctrl: correct a offset while enumerating
> pins
> 
> On Tue, Jan 3, 2012 at 8:47 AM, Chanho Park <chanho61.park@samsung.com>
> wrote:
> 
> This:
> 
> > -               /* Pin space may be sparse */
> > +               /* Skip if we cannot search the pin */
> (...)
> > -               /* Pin space may be sparse */
> > +               /* Skip if we cannot search the pin */
> 
> I don't see why you're changing that comment, it is still true that
> the pin space may be sparse and that is what your patch confirms.
> 
> So I will restore that comment...

We do not concern that pin space is sparse
because we enumerate the pin space using the offset of array.
This situation is that we cannot search the pin from radix tree.
It is BUGON() or just skip this pin :)

Best regards,
Chanho Park


  reply	other threads:[~2012-01-03  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03  7:47 [PATCH 0/2] add support for partial pin space Chanho Park
2012-01-03  7:47 ` [PATCH 1/2] pinctrl: correct a offset while enumerating pins Chanho Park
2012-01-03  7:58   ` Linus Walleij
2012-01-03  8:37     ` Chanho Park [this message]
2012-01-04  9:37       ` Linus Walleij
2012-01-03  7:47 ` [PATCH 2/2] pinctrl: remove unnecessary max pin number Chanho Park
2012-01-03  7:57 ` [PATCH 0/2] add support for partial pin space Linus Walleij
2012-01-03  8:27   ` Chanho Park

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='008001ccc9f2$f38fadd0$daaf0970$%park@samsung.com' \
    --to=chanho61.park@samsung.com \
    --cc=Baohua.Song@csr.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.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®