From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3 v5] stdio/device: rework function naming convention
Date: Tue, 19 May 2009 14:54:09 +0200 [thread overview]
Message-ID: <20090519125409.GU17539@game.jcrosoft.org> (raw)
In-Reply-To: <1242468896-5007-1-git-send-email-plagnioj@jcrosoft.com>
On 12:14 Sat 16 May , Jean-Christophe PLAGNIOL-VILLARD wrote:
> actually the console API use the following naming convention
>
> ======Extract======
> typedef struct device_t;
>
> int device_register (device_t * dev);
> int devices_init (void);
> int device_deregister(char *devname);
> struct list_head* device_get_list(void);
> device_t* device_get_by_name(char* name);
> device_t* device_clone(device_t *dev);
> =======
>
> which is device generic and confusing
>
> instead of using device_XX and device_t
> we now switch to stdio_XX and stdio_dev
>
> this will also allow to add later a generic device mecanism
> in order to have multi generic device support and driver instance
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> ---
ping
Best Regards,
J.
next prev parent reply other threads:[~2009-05-19 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 10:14 [U-Boot] [PATCH 1/3 v5] stdio/device: rework function naming convention Jean-Christophe PLAGNIOL-VILLARD
2009-05-16 10:14 ` [U-Boot] [PATCH 2/3 v5] console: unify printing current devices Jean-Christophe PLAGNIOL-VILLARD
2009-05-16 10:14 ` [U-Boot] [PATCH 3/3 v5] mpl: printing current stdio devices cleanup Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 23:17 ` Wolfgang Denk
2009-07-18 23:03 ` [U-Boot] [PATCH 2/3 v5] console: unify printing current devices Wolfgang Denk
2009-05-19 12:54 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-07-09 20:47 ` [U-Boot] [PATCH 1/3 v5] stdio/device: rework function naming convention Jean-Christophe PLAGNIOL-VILLARD
2009-07-17 22:35 ` Wolfgang Denk
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=20090519125409.GU17539@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=u-boot@lists.denx.de \
/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