[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1336992089-2733-1-git-send-email-siglesias@igalia.com>
Date: Mon, 14 May 2012 12:41:24 +0200
From: Samuel Iglesias Gonsalvez <siglesias@...lia.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Samuel Iglesias Gonsalvez <siglesias@...lia.com>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] Staging ipack: device model and clean-up
Hello,
These patches introduce some clean-up code and fix one bug related to the
presence of ipack_driver ops.
The big change is added by [PATCH 2/5] where it adds a better support to device
model in the ipack driver.
All the devices (carrier and mezzanine boards) are ipack_devices and it is
needed to make a relation between an ipack_device and an ipack_driver using
the provided match/probe functions.
Doing that, it is possible to represent the relation between each carrier and
mezzanines plugged to it through sysfs and, also, between each device and its
driver.
These patches apply on top of the previous ones:
http://lkml.indiana.edu/hypermail/linux/kernel/1205.1/02410.html
Thanks,
Sam
Samuel Iglesias Gonsalvez (5):
Staging ipack: fix a few sparse warnings
Staging: ipack: add proper device model into ipack_bus_register.
Staging: ipack: remove board_name and bus_name fields from struct
ipack_device
Staging ipack/bridges/tpci200: remove TPCI200_SHORTNAME constant
Staging: ipack/devices/ipoctal: check for availability of helper
functions in ipoctal_match()
drivers/staging/ipack/bridges/tpci200.c | 225 ++++++++++++++++---------------
drivers/staging/ipack/bridges/tpci200.h | 18 ++-
drivers/staging/ipack/devices/ipoctal.c | 12 +-
drivers/staging/ipack/ipack.c | 68 ++++++++--
drivers/staging/ipack/ipack.h | 61 ++++-----
5 files changed, 220 insertions(+), 164 deletions(-)
--
1.7.10
--
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