From: Grant Likely <grant.likely@secretlab.ca>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>,
Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>
Subject: Re: [PATCH v2] gpio/omap: fix incorrect initialization of omap_gpio_mod_init
Date: Fri, 11 May 2012 12:58:33 -0600 [thread overview]
Message-ID: <20120511185834.08DAB3E0791@localhost> (raw)
In-Reply-To: <CAC83ZvLYmPr3qTRUUTom1iOA-czef9EVcM229UMDePnw8sbA+w@mail.gmail.com>
On Mon, 7 May 2012 10:52:28 +0530, "DebBarma, Tarun Kanti" <tarun.kanti@ti.com> wrote:
> Hi,
>
> On Sun, May 6, 2012 at 3:25 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
> > I've noticed that current mainline enables _all_ possible GPIO
> > interrupts, this patch fixes that problem.
> OK, thanks.
>
> > Also Grant doesn't seem to be on CC so might not be able to pick this up.
> I have added Cc: in the patch and was expecting that would take care.
> Looks like that has not happened. Anyways, I have explicitly added in the email.
I'm particularly bursty when it comes to patch review and applying.
Sometimes it takes me a while to find time for maintainership work.
g.
WARNING: multiple messages have this Message-ID (diff)
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] gpio/omap: fix incorrect initialization of omap_gpio_mod_init
Date: Fri, 11 May 2012 12:58:33 -0600 [thread overview]
Message-ID: <20120511185834.08DAB3E0791@localhost> (raw)
In-Reply-To: <CAC83ZvLYmPr3qTRUUTom1iOA-czef9EVcM229UMDePnw8sbA+w@mail.gmail.com>
On Mon, 7 May 2012 10:52:28 +0530, "DebBarma, Tarun Kanti" <tarun.kanti@ti.com> wrote:
> Hi,
>
> On Sun, May 6, 2012 at 3:25 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
> > I've noticed that current mainline enables _all_ possible GPIO
> > interrupts, this patch fixes that problem.
> OK, thanks.
>
> > Also Grant doesn't seem to be on CC so might not be able to pick this up.
> I have added Cc: in the patch and was expecting that would take care.
> Looks like that has not happened. Anyways, I have explicitly added in the email.
I'm particularly bursty when it comes to patch review and applying.
Sometimes it takes me a while to find time for maintainership work.
g.
next prev parent reply other threads:[~2012-05-11 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 7:20 [PATCH v2] gpio/omap: fix incorrect initialization of omap_gpio_mod_init Tarun Kanti DebBarma
2012-04-30 7:20 ` Tarun Kanti DebBarma
2012-05-05 21:55 ` Grazvydas Ignotas
2012-05-05 21:55 ` Grazvydas Ignotas
2012-05-07 5:22 ` DebBarma, Tarun Kanti
2012-05-07 5:22 ` DebBarma, Tarun Kanti
2012-05-09 21:36 ` Janusz Krzysztofik
2012-05-09 21:36 ` Janusz Krzysztofik
2012-05-10 5:15 ` DebBarma, Tarun Kanti
2012-05-10 5:15 ` DebBarma, Tarun Kanti
2012-05-10 14:23 ` Kevin Hilman
2012-05-10 14:23 ` Kevin Hilman
2012-05-11 18:57 ` Grant Likely
2012-05-11 18:57 ` Grant Likely
2012-05-11 18:58 ` Grant Likely [this message]
2012-05-11 18:58 ` Grant Likely
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=20120511185834.08DAB3E0791@localhost \
--to=grant.likely@secretlab.ca \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=tarun.kanti@ti.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 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.