From: Felipe Contreras <felipe.contreras@gmail.com>
To: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Ameya Palande <ameya.palande@nokia.com>,
Hiroshi Doyu <Hiroshi.DOYU@nokia.com>,
Felipe Contreras <felipe.contreras@nokia.com>,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 0/2] dspbridge: reorganize initialization and probe
Date: Wed, 9 Jun 2010 10:25:17 +0300 [thread overview]
Message-ID: <AANLkTil4gAHQcEdAedxamD9mi5d-0CxGLqP_8h9vY77j@mail.gmail.com> (raw)
In-Reply-To: <1276044493-23003-1-git-send-email-omar.ramirez@ti.com>
On Wed, Jun 9, 2010 at 3:48 AM, Omar Ramirez Luna <omar.ramirez@ti.com> wrote:
> Split the functions to have cleaner error handling paths, this
> will aslo cover a case where bridge initialization has failed but
> device entry is still available which leads to unknown behavior.
Great, I was wondering why this was not the case.
Now that you are on this, do you know if there's something missing in
order to automatically load the module when somebody tries to open
/dev/DspBridge?
--
Felipe Contreras
next prev parent reply other threads:[~2010-06-09 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 0:48 [PATCH 0/2] dspbridge: reorganize initialization and probe Omar Ramirez Luna
2010-06-09 0:48 ` [PATCH 1/2] DSPRBIDGE: split probe from bridge initializations Omar Ramirez Luna
2010-06-09 0:48 ` [PATCH 2/2] DSPBRIDGE: reorganize probe function Omar Ramirez Luna
2010-06-09 7:25 ` Felipe Contreras [this message]
2010-06-09 8:49 ` [PATCH 0/2] dspbridge: reorganize initialization and probe Ameya Palande
2010-06-09 9:28 ` Felipe Contreras
2010-06-14 17:59 ` Ramirez Luna, Omar
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=AANLkTil4gAHQcEdAedxamD9mi5d-0CxGLqP_8h9vY77j@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=omar.ramirez@ti.com \
/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 NNTP newsgroup(s).