From: Tony Lindgren <tony@atomide.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/7] omap hsmmc init cleanup and section warning fixes for v3.4 merge window
Date: Thu, 23 Feb 2012 10:52:17 -0800 [thread overview]
Message-ID: <20120223185217.GY18185@atomide.com> (raw)
In-Reply-To: <1329997247-27342-1-git-send-email-rnayak@ti.com>
* Rajendra Nayak <rnayak@ti.com> [120223 03:09]:
> Re-sending as these patches did not make it to the lists due to
> issues with my 'git send-email'
>
> Hi Tony,
>
> This is a re-spin of your series to fix up the section
> mismatch warnings noted by Russell with omap2_hsmmc_init().
> The previous series had an issue around multiple insmod/rmmod
> of the twl4030 gpio driver when built as a module as reported
> by Russell again.
OK, can you please rebase your patches on hsmmc branch in linux-omap
at commit 0e91c8ddf0e0932da59ec1d116e34049791b0e73?
Note that at least the hardcoded GPIO numbers are no longer needed.
> There were 2 issues, one with gpio_requests failing as they were
> never freed on the module unload/unbind. The other was with the
> mmc devices being registered again. I have fixed both these issues
> in this series, mainly by having a .teardown hook for twl4030 gpio
> driver populated from all OMAP3 board files, which release all the
> requested gpios and also unregister the mmc omap/platform device.
Yes that's great.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] omap hsmmc init cleanup and section warning fixes for v3.4 merge window
Date: Thu, 23 Feb 2012 10:52:17 -0800 [thread overview]
Message-ID: <20120223185217.GY18185@atomide.com> (raw)
In-Reply-To: <1329997247-27342-1-git-send-email-rnayak@ti.com>
* Rajendra Nayak <rnayak@ti.com> [120223 03:09]:
> Re-sending as these patches did not make it to the lists due to
> issues with my 'git send-email'
>
> Hi Tony,
>
> This is a re-spin of your series to fix up the section
> mismatch warnings noted by Russell with omap2_hsmmc_init().
> The previous series had an issue around multiple insmod/rmmod
> of the twl4030 gpio driver when built as a module as reported
> by Russell again.
OK, can you please rebase your patches on hsmmc branch in linux-omap
at commit 0e91c8ddf0e0932da59ec1d116e34049791b0e73?
Note that at least the hardcoded GPIO numbers are no longer needed.
> There were 2 issues, one with gpio_requests failing as they were
> never freed on the module unload/unbind. The other was with the
> mmc devices being registered again. I have fixed both these issues
> in this series, mainly by having a .teardown hook for twl4030 gpio
> driver populated from all OMAP3 board files, which release all the
> requested gpios and also unregister the mmc omap/platform device.
Yes that's great.
Regards,
Tony
next prev parent reply other threads:[~2012-02-23 18:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 11:40 [PATCH v2 0/7] omap hsmmc init cleanup and section warning fixes for v3.4 merge window Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 1/7] ARM: OMAP: omap_device: Expose omap_device_{alloc, delete, register} Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 2/7] ARM: OMAP: omap_device: Add omap_device_unregister() Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 3/7] mmc: omap_hsmmc: Make the driver support hotpluggable devices Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 4/7] mmc: omap_hsmmc: If probe fails, give our error messages Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 5/7] ARM: OMAP2+: Split omap2_hsmmc_init() to properly support I2C GPIO pins Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 14:28 ` Igor Grinberg
2012-02-23 14:28 ` Igor Grinberg
2012-02-23 18:47 ` Tony Lindgren
2012-02-23 18:47 ` Tony Lindgren
2012-02-24 4:11 ` Rajendra Nayak
2012-02-24 4:11 ` Rajendra Nayak
2012-02-24 7:01 ` Igor Grinberg
2012-02-24 7:01 ` Igor Grinberg
2012-02-24 22:19 ` Tony Lindgren
2012-02-24 22:19 ` Tony Lindgren
2012-02-24 3:24 ` Rajendra Nayak
2012-02-24 3:24 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 6/7] ARM: OMAP3: Use .teardown of twl4030-gpio to clean board requests Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-02-23 14:55 ` Igor Grinberg
2012-02-23 14:55 ` Igor Grinberg
2012-02-24 3:43 ` Rajendra Nayak
2012-02-24 3:43 ` Rajendra Nayak
2012-02-23 11:40 ` [PATCH v2 7/7] ARM: OMAP2+: Mark omap_hsmmc_init and omap_mux related functions as __init Rajendra Nayak
2012-02-23 11:40 ` Rajendra Nayak
2012-03-19 9:08 ` Tomi Valkeinen
2012-03-19 9:08 ` Tomi Valkeinen
2012-03-19 10:20 ` Tomi Valkeinen
2012-03-19 10:20 ` Tomi Valkeinen
2012-03-19 18:09 ` Tony Lindgren
2012-03-19 18:09 ` Tony Lindgren
2012-03-20 7:30 ` Tomi Valkeinen
2012-03-20 7:30 ` Tomi Valkeinen
2012-03-20 22:17 ` Tony Lindgren
2012-03-20 22:17 ` Tony Lindgren
2012-02-23 18:52 ` Tony Lindgren [this message]
2012-02-23 18:52 ` [PATCH v2 0/7] omap hsmmc init cleanup and section warning fixes for v3.4 merge window Tony Lindgren
2012-02-24 4:14 ` Rajendra Nayak
2012-02-24 4:14 ` Rajendra Nayak
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=20120223185217.GY18185@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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.