[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1314785146-19163-1-git-send-email-manohar.vanga@cern.ch>
Date: Wed, 31 Aug 2011 12:05:43 +0200
From: Manohar Vanga <manohar.vanga@...n.ch>
To: <gregkh@...e.de>
CC: <martyn.welch@...com>, <cota@...ap.org>,
<devel@...verdev.osuosl.org>, <linux-kernel@...r.kernel.org>,
Manohar Vanga <manohar.vanga@...n.ch>
Subject: [PATCH 0/3] [RESEND v4] VME Framework Fixes
Hi Greg, Martyn,
I have reordered the patches to separate the bridge refcounting patch
for now so that we can make some progress on getting the other patches
into the tree. I will rework the refcounting patch and send it later.
Please review these patches and let me know if I missed anything (quite
likely). A note on the various patches follows:
* staging: vme: change static device array to pointers
This patch changes the static array of devices to an array of
pointers that are dynamically allocated. Hopefully I understood
what you meant correctly and the changes are sufficient. I assume
you were referring to the requirement that all kobjects be allocated
dynamically and never statically (found in Documentation/kobject.txt).
* staging: vme: add struct vme_dev for VME devices
* staging: vme: make match() driver specific to improve non-VME64x
support
Changes based on the moving of the bridge refcounting patch as well
as changes based on comments from Emilio and Greg in the last resend.
Thanks!
Manohar
Manohar Vanga (3):
staging: vme: change static device array to pointers
staging: vme: add struct vme_dev for VME devices
staging: vme: make match() driver specific to improve non-VME64x
support
drivers/staging/vme/devices/vme_user.c | 67 +++-----
drivers/staging/vme/devices/vme_user.h | 2 +-
drivers/staging/vme/vme.c | 274 +++++++++++++++-----------------
drivers/staging/vme/vme.h | 55 +++++--
drivers/staging/vme/vme_api.txt | 79 ++++++----
drivers/staging/vme/vme_bridge.h | 5 -
6 files changed, 244 insertions(+), 238 deletions(-)
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists