From: Linus Walleij <linus.walleij@linaro.org>
To: Kevin Hilman <khilman@ti.com>
Cc: Tarun Kanti DebBarma <tarun.kanti@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver
Date: Thu, 12 Jul 2012 13:03:00 +0200 [thread overview]
Message-ID: <CACRpkdZMG_ZHW_eGGrdrJh1SuO_=hOObijzmxG1ob6RoNf_dwg@mail.gmail.com> (raw)
In-Reply-To: <87394xhocn.fsf@ti.com>
On Thu, Jul 12, 2012 at 1:25 AM, Kevin Hilman <khilman@ti.com> wrote:
> There is quite a bit of other things to do in remove to properly cleanup
> what is done in probe.
OK I'm dropping this patch for now...
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver
Date: Thu, 12 Jul 2012 13:03:00 +0200 [thread overview]
Message-ID: <CACRpkdZMG_ZHW_eGGrdrJh1SuO_=hOObijzmxG1ob6RoNf_dwg@mail.gmail.com> (raw)
In-Reply-To: <87394xhocn.fsf@ti.com>
On Thu, Jul 12, 2012 at 1:25 AM, Kevin Hilman <khilman@ti.com> wrote:
> There is quite a bit of other things to do in remove to properly cleanup
> what is done in probe.
OK I'm dropping this patch for now...
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-07-12 11:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 9:13 [PATCH 0/2] gpio/omap: few code realignment and update of missing code Tarun Kanti DebBarma
2012-07-11 9:13 ` Tarun Kanti DebBarma
2012-07-11 9:13 ` Tarun Kanti DebBarma
2012-07-11 9:13 ` [PATCH 1/2] gpio/omap: move bank->dbck initialization to omap_gpio_mod_init() Tarun Kanti DebBarma
2012-07-11 9:13 ` Tarun Kanti DebBarma
2012-07-11 9:13 ` Tarun Kanti DebBarma
2012-07-11 17:51 ` Paul Walmsley
2012-07-11 17:51 ` Paul Walmsley
2012-07-11 17:56 ` DebBarma, Tarun Kanti
2012-07-11 17:56 ` DebBarma, Tarun Kanti
2012-07-11 21:51 ` Linus Walleij
2012-07-11 21:51 ` Linus Walleij
2012-07-11 9:13 ` [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver Tarun Kanti DebBarma
2012-07-11 9:13 ` Tarun Kanti DebBarma
2012-07-11 9:13 ` Tarun Kanti DebBarma
2012-07-11 21:54 ` Linus Walleij
2012-07-11 21:54 ` Linus Walleij
2012-07-11 23:25 ` Kevin Hilman
2012-07-11 23:25 ` Kevin Hilman
2012-07-11 23:25 ` Kevin Hilman
2012-07-12 11:03 ` Linus Walleij [this message]
2012-07-12 11:03 ` Linus Walleij
2012-07-12 17:48 ` Kevin Hilman
2012-07-12 17:48 ` Kevin Hilman
2012-07-12 17:48 ` Kevin Hilman
2012-07-14 20:51 ` Linus Walleij
2012-07-14 20:51 ` Linus Walleij
2012-07-16 17:10 ` Kevin Hilman
2012-07-16 17:10 ` Kevin Hilman
2012-07-16 17:10 ` Kevin Hilman
2012-07-16 20:49 ` Linus Walleij
2012-07-16 20:49 ` Linus Walleij
2012-07-16 22:01 ` Kevin Hilman
2012-07-16 22:01 ` Kevin Hilman
2012-07-16 22:01 ` Kevin Hilman
2012-07-17 6:03 ` Shilimkar, Santosh
2012-07-17 6:03 ` Shilimkar, Santosh
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='CACRpkdZMG_ZHW_eGGrdrJh1SuO_=hOObijzmxG1ob6RoNf_dwg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.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.