From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001816] New: Allow non const cyg_i2c_device for I2C callback functions.
Date: Wed, 10 Apr 2013 20:54:00 -0000 [thread overview]
Message-ID: <bug-1001816-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001816
Bug ID: 1001816
Summary: Allow non const cyg_i2c_device for I2C callback
functions.
Product: eCos
Version: CVS
Target: All
Architecture/Host Other
OS:
Status: NEW
Severity: enhancement
Priority: low
Component: Patches and contributions
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: ilijak@siva.com.mk
CC: ecos-patches@ecos.sourceware.org
Blocks: 1001397
Created attachment 2178
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2178&action=edit
A patch that allows override of const attribute.
The structure cyg_i2c_bus declares a number of callback functions. Some
functions have an argument of type const cyg_i2c_device*. In some cases ability
to modify cyg_i2c_device may be beneficial so it would be useful to remove
const attribute. The example is Kinetis I2C driver (bug 1001397) that uses
cyg_delay field for caching of frequency divider once it is computed.
The submitted patch provides a possibility for individual driver to override
const attribute.
Ilija
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-04-10 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 20:54 bugzilla-daemon [this message]
2013-04-25 17:11 ` [Bug 1001816] " bugzilla-daemon
2013-04-26 17:13 ` bugzilla-daemon
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=bug-1001816-104@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).