From: Dirk Behme <dirk.behme@googlemail.com>
To: tony@atomide.com, Komal Shah <komal_shah802003@yahoo.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending October patches
Date: Thu, 02 Nov 2006 18:00:33 +0100 [thread overview]
Message-ID: <454A2431.9010007@gmail.com> (raw)
In-Reply-To: <20061101212850.GD6833@atomide.com>
tony@atomide.com wrote:
>>9. [PATCH] ARM: OMAP: Fix warnings in plat-omap/dsp
>>http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008185.html
>
> I think the unlikely() is unlikely necessary for init and sysfs?
Thanks for review! It was just a mechanical search & replace
without any look to the functions itself. Will update this
and the others soon.
>>26. [PATCH] ARM: OMAP: Make AIC23 sound work again
>>http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008232.html
>
> Hmmm, I think there were some comments on this hack on LKML when we
> merged the driver?
Komal, what do you think here?
Anybody aware of someone working on a better solution? Any
link to the LKML discussion about this?
Best regards
dirk
next prev parent reply other threads:[~2006-11-02 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 15:54 Pending October patches Dirk Behme
2006-11-01 21:28 ` tony
2006-11-02 17:00 ` Dirk Behme [this message]
2006-11-03 10:50 ` Komal Shah
2006-11-05 10:32 ` I2C zero length transfers and SMBUS_QUICK, was: " Dirk Behme
2006-11-05 19:49 ` Komal Shah
2006-11-06 10:36 ` Arnaud Patard
2006-11-06 18:33 ` Broken N770, was: I2C zero length transfers and SMBUS_QUICK Dirk Behme
2006-11-06 19:49 ` Arnaud Patard
2006-11-06 20:18 ` Broken N770 Dirk Behme
2006-11-06 20:24 ` Arnaud Patard
2006-11-06 1:37 ` I2C zero length transfers and SMBUS_QUICK, was: Pending October patches David Brownell
2006-11-07 17:40 ` tony
2006-11-07 20:24 ` I2C zero length transfers and SMBUS_QUICK David Brownell
2006-11-09 2:32 ` Tony Lindgren
2006-11-03 19:52 ` Pending October patches David Brownell
2006-11-03 20:18 ` Dirk Behme
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=454A2431.9010007@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=komal_shah802003@yahoo.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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