On 08/01/2011 01:54 PM, Dan Carpenter wrote:
On Thu, Jul 14, 2011 at 02:29:14PM -0700, Franky Lin wrote:
From: Arend van Spriel<arend@xxxxxxxxxxxx>
The semaphore proto_sem has been replaced with mutex proto_block
which lock certain code paths for one thread.
This one doesn't apply any more after the 3.1 merge window.
It was modified in 1380516599 "Merge branch 'staging-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6"
regards,
dan carpenter
Hi Dan,
Thanks for the heads up. We sent three patch series that have not been
taken into staging-next due to the merge window. I tried looking for
the commit id you mention (if it is one), but no luck in any common repo
on git.kernel.org. Also I don't see a 3.1-rc1 tag yet.
I suspect we have to resend all three patch series once 3.1-rc1 is ready
and available in Greg's staging repo. At least the patches have been on
the mailing list long enough for people to provide us with comments. I
already saw some of our source files mentioned in the merge of
staging-next branch by Linus so I already had my suspicions regarding
the patch series.
Gr. AvS
--
Almost nobody dances sober, unless they happen to be insane.
-- H.P. Lovecraft --
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html