From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: device parameter patches
Date: Tue, 24 Apr 2012 11:21:16 +0200 [thread overview]
Message-ID: <1335259279-25353-1-git-send-email-s.hauer@pengutronix.de> (raw)
Some device parameter patches.
Sascha
----------------------------------------------------------------
Sascha Hauer (3):
param: make return value of param getter function const
devinfo: use accessor function for parameters
dev_add_param: check if param exists already
drivers/base/driver.c | 2 +-
include/param.h | 6 +++---
lib/parameter.c | 14 +++++++++-----
3 files changed, 13 insertions(+), 9 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-04-24 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 9:21 Sascha Hauer [this message]
2012-04-24 9:21 ` [PATCH 1/3] param: make return value of param getter function const Sascha Hauer
2012-04-24 9:21 ` [PATCH 2/3] devinfo: use accessor function for parameters Sascha Hauer
2012-04-24 9:21 ` [PATCH 3/3] dev_add_param: check if param exists already Sascha Hauer
2012-05-13 12:04 device parameter patches Sascha Hauer
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=1335259279-25353-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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