From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] i2c: add i2c_core and prepare for new multibus support
Date: Wed, 18 Jan 2012 14:43:28 -0600 [thread overview]
Message-ID: <4F172EF0.3040408@freescale.com> (raw)
In-Reply-To: <201201181541.42710.vapier@gentoo.org>
Mike Frysinger wrote:
> that's only needed if you expect the pointer to stay valid across calls. i
> don't think it does for most (all?) drivers.
True, but it's hard to know sometimes when it's needed. I do it in my
code just to be sure.
Regardless, I still think the idea of a "current" i2c bus is flawed.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-01-18 20:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 7:12 [U-Boot] [PATCH 0/3] Bring in new I2C framework Simon Glass
2012-01-17 7:12 ` [U-Boot] [PATCH 1/3] i2c: add i2c_core and prepare for new multibus support Simon Glass
2012-01-17 19:23 ` Mike Frysinger
2012-01-18 20:11 ` Tabi Timur-B04825
2012-01-18 20:41 ` Mike Frysinger
2012-01-18 20:43 ` Timur Tabi [this message]
2012-01-18 21:37 ` Simon Glass
2012-01-18 21:39 ` Timur Tabi
2012-01-18 22:21 ` Simon Glass
2012-01-18 22:24 ` Timur Tabi
2012-01-19 5:36 ` Wolfgang Denk
2012-01-19 6:35 ` Heiko Schocher
2012-01-19 6:53 ` Simon Glass
2012-01-19 7:53 ` Heiko Schocher
2012-01-19 18:07 ` Simon Glass
2012-01-19 11:20 ` Wolfgang Denk
2012-01-19 18:10 ` Simon Glass
2012-01-19 18:47 ` Timur Tabi
2012-01-20 6:50 ` Heiko Schocher
2012-01-17 7:12 ` [U-Boot] [PATCH 2/3] i2c: common changes for multibus/multiadapter support Simon Glass
2012-01-17 7:12 ` [U-Boot] [PATCH 3/3] WIP: tegra: i2c: Enable new I2C framework Simon Glass
2012-01-17 8:51 ` Heiko Schocher
2012-01-17 8:30 ` [U-Boot] [PATCH 0/3] Bring in " Heiko Schocher
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 17:40 Heiko Schocher
2012-10-22 17:40 ` [U-Boot] [PATCH 1/3] i2c: add i2c_core and prepare for new multibus support Heiko Schocher
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=4F172EF0.3040408@freescale.com \
--to=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.