From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, xsonnek@gmail.com,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 1/1] semaphore: declare down_try
Date: Wed, 30 Jul 2008 09:48:17 -0700 [thread overview]
Message-ID: <20080730094817.135cdbfa.akpm@linux-foundation.org> (raw)
In-Reply-To: <48905028.5060908@gmail.com>
On Wed, 30 Jul 2008 13:27:36 +0200 Jiri Slaby <jirislaby@gmail.com> wrote:
> Jiri Slaby napsal(a):
> > Maybe you already fixed this, in todays mmotm there is a fix of duplicate
> > down_try definiton, but this problem still persist.
>
> BTW. there is still bunch of down_trylock(); users, are you about to
> eliminate them?
>
> 2 182 /home/latest/xxx/drivers/watchdog/ar7_wdt.c <<ar7_wdt_open>>
> if (down_trylock(&open_semaphore))
> 3 309 /home/latest/xxx/drivers/watchdog/it8712f_wdt.c
> <<it8712f_wdt_open>>
> if (down_trylock(&it8712f_wdt_sem))
> 4 214 /home/latest/xxx/drivers/watchdog/s3c2410_wdt.c
> <<s3c2410wdt_open>>
> if(down_trylock(&open_lock))
> 5 154 /home/latest/xxx/drivers/watchdog/sc1200wdt.c <<sc1200wdt_open>>
> if (down_trylock(&open_sem))
> 6 95 /home/latest/xxx/drivers/watchdog/scx200_wdt.c <<scx200_wdt_open>>
> if (down_trylock(&open_semaphore))
> 7 429 /home/latest/xxx/drivers/watchdog/wdt_pci.c <<wdtpci_open>>
> if (down_trylock(&open_sem))
oh crap, yes, sorry, I had a bit of a catastrophe with two different
versions of the sameish thing coming from two directions and my
approach to fixing that was to drop one patch and to await the next
linux-next pull for the other. Forgot.
prev parent reply other threads:[~2008-07-30 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 11:25 [PATCH 1/1] semaphore: declare down_try Jiri Slaby
2008-07-30 11:27 ` Jiri Slaby
2008-07-30 16:48 ` Andrew Morton [this message]
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=20080730094817.135cdbfa.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=xsonnek@gmail.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