linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH resend v3 0/2] mmc: Add SDIO function devicetree subnode parsing
@ 2014-06-30  9:07 Hans de Goede
  2014-06-30  9:07 ` [PATCH resend v3 1/2] dt: bindings: mmc: Add sdio function subnode documentation Hans de Goede
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Hans de Goede @ 2014-06-30  9:07 UTC (permalink / raw)
  To: linux-arm-kernel

Hi All,

Here is a resend of 3 of my submission of Sascha Hauer's
"mmc: Add SDIO function devicetree subnode parsing" patch.

Can we please get some movement on these patches, either a review specifying
why this cannot go upstream, or else queuing it up for next / 3.17 ?

Changes since v1:
- Submit as a stand-alone patch-set, rather then as part of a larger oob irq
  support patchset crossing multiple subsystems
- Add a patch to document the already existing practice of using slot subnodes
- Split of the dt bindings documentation for sdio-func child nodes into its
  own patch
- Add a preparation patch, setting slot_no where relevant
- And finally the "Add SDIO function devicetree subnode parsing" patch itself
  has been modified to look for the sdio function childnodes under a slot node
  instead of directly under the host node

Changes since v2:
- Drop the slot subnodes again, and drop the 2 slot subnodes patches

Regards,

Hans 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-01-02 15:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-30  9:07 [PATCH resend v3 0/2] mmc: Add SDIO function devicetree subnode parsing Hans de Goede
2014-06-30  9:07 ` [PATCH resend v3 1/2] dt: bindings: mmc: Add sdio function subnode documentation Hans de Goede
2014-06-30  9:07 ` [PATCH resend v3 2/2] mmc: Add SDIO function devicetree subnode parsing Hans de Goede
2015-01-02 15:52 ` [PATCH resend v3 0/2] " Ulf Hansson

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).