mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@home-tj.org>
To: rusty@rustcorp.com.au, mochel@osdl.org, greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.10-rc1 0/15] driver-model: per-device parameter, round 3
Date: Thu, 4 Nov 2004 15:35:32 +0900	[thread overview]
Message-ID: <20041104063532.GA24566@home-tj.org> (raw)

 Hello, guys.

 This is the third round of devparam patches.  I think it's mostly
ready now.  Changes from the last round include

 1. vector is gone.  BTW, I found out that implementing simple
vector-like thing inside devparam looked quite okay.  I actually like
this way better now.  :-)

 2. KPARAM_NO_RANGE added.  Unfortunately, macros still need to use
explicit 1, 0 as KPARAM_NO_RANGE is recognized as one argument rather
than two for macros.  However, all those macros are right under the
definition of its ranged counterpart, so I don't think it will cause
any confusion.

 3. DEFINE_DEVICE_PARAMSET_NS() added.  This macros accepts one
additional argument - @Namespace.  All parameters defined inside this
macro are assumed to have dot-appened @Namespace as their prefix.
Please read Documentation/devparam.txt for more details.

 4. parameters subdirectory handling fixed and improved.  Also,
parameters subdirectory isn't created when no devparam is used.


 Regarding the last posting, Rusty, parameters subdirectory rename is
not really a user-visible breakage.  It hasn't seen the light of day,
yet.  I was talking about parameters subdirectory under the device's
sysfs node.

 I'm also posting another set of patches for device manual attach.
This was what I was aiming for from the start.  This basically dumps
device-driver association management to user-space and allows
user-space to specify the driver to attach to and what arguments to
use when attaching.  I'll write more about it when I post the patches.

 Whether manualattach is accepted or not, manualattach at least will
show that devparam implements per-device parameter which can be
specified dynamically while maintaining backward compatibility (No
user-visible breakage!).

 All patches are against a freshly updated Linus bk tree and as
before, the updated document and dptest module source codes are at

http://home-tj.org/devparam/devparam.txt
http://home-tj.org/devparam/dptest.tar.gz

 Also, all patches are available at the following URL.

http://home-tj.org/devparam/20041104/

 I believe inssues are mostly resolved and devparam is ready to be
tested now.  Please consider accepting it or tell me what you guys
dislike.  I'll fix'em ASAP.  :-)

 Thanks.

-- 
tejun


             reply	other threads:[~2004-11-04  6:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04  6:35 Tejun Heo [this message]
2004-11-04  6:38 ` [PATCH 2.6.10-rc1 1/15] driver-model: param_array_set num field fix Tejun Heo
2004-11-04  6:39 ` [PATCH 2.6.10-rc1 2/15] driver-model: flag type helpers added to moduleparam Tejun Heo
2004-11-04  6:40 ` [PATCH 2.6.10-rc1 3/15] driver-model: Tejun Heo
2004-11-04  6:44 ` [PATCH 2.6.10-rc1 4/15] driver-model: const qualifier removed from @val of param_array() Tejun Heo
2004-11-04  6:45 ` [PATCH 2.6.10-rc1 5/15] driver-model: param_array_delims() implemented Tejun Heo
2004-11-04  6:47 ` [PATCH 2.6.10-rc1 6/15] driver-model: ':' added to default param_array delimiters Tejun Heo
2004-11-04  6:48 ` [PATCH 2.6.10-rc1 7/15] driver-model: next_arg() renamed to param_next_arg() and became global Tejun Heo
2004-11-04  6:49 ` [PATCH 2.6.10-rc1 8/15] driver-model: MODULE_PARAM_PREFIX is changed to empty string from nothing Tejun Heo
2004-11-04  6:50 ` [PATCH 2.6.10-rc1 9/15] driver-model: parse_args()'s @unknown function modified to take void *arg Tejun Heo
2004-11-04  6:51 ` [PATCH 2.6.10-rc1 10/15] driver-model: module_param_array() changed back to accept variable name directly for @num and module_param_arr() added Tejun Heo
2004-11-04  6:52 ` [PATCH 2.6.10-rc1 11/15] driver-model: module_param_array/arr() change applied Tejun Heo
2004-11-04  6:53 ` [PATCH 2.6.10-rc1 12/15] driver-model: devparam implemented Tejun Heo
2004-11-04  6:53 ` [PATCH 2.6.10-rc1 13/15] driver-model: devparam applied Tejun Heo
2004-11-04  6:54 ` [PATCH 2.6.10-rc1 14/15] driver-model: devparam documentation Tejun Heo
2004-11-04  6:54 ` [PATCH 2.6.10-rc1 15/15] driver-model: via-velocity converted to use devparam Tejun Heo

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=20041104063532.GA24566@home-tj.org \
    --to=tj@home-tj.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=rusty@rustcorp.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®