From: Richard Zidlicky <rz@linux-m68k.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: schedule inside spin_lock_irqsave?
Date: Tue, 1 Jun 2010 19:17:10 +0200 [thread overview]
Message-ID: <20100601171710.GA5176@linux-m68k.org> (raw)
In-Reply-To: <4C0284FF.4080707@gmail.com> <4C028336.8030704@gmail.com>
On Sun, May 30, 2010 at 05:24:38PM +0200, Jiri Slaby wrote:
Hi,
> > came across following snippet of code (2.6.34:drivers/media/dvb/siano/smscoreapi.c) and
...
...
...
> This should be
> wait_event(&coredev->buffer_mng_waitq, cb = get_entry());
> with get_entry like:
> struct smscore_buffer_t *get_entry(void)
> {
> struct smscore_buffer_t *cb = NULL;
> spin_lock_irqsave(&coredev->bufferslock, flags);
> if (!list_empty(&coredev->buffers)) {
> cb = (struct smscore_buffer_t *) coredev->buffers.next;
> list_del(&cb->entry);
> }
> spin_unlock_irqrestore(&coredev->bufferslock, flags);
> return cb;
> }
...
...
...
>
> Looking at the smscore_buffer_t definition, this is really ugly since it
> relies on entry being the first in the structure. It should be
> list_first_entry(&coredev->buffers, ...) instead, cast-less.
>
> > list_del(&cb->entry);
> > }
> > spin_unlock_irqrestore(&coredev->bufferslock, flags);
> > return cb;
> > }
thanks for the suggestions, is it on anyones TODO list or should I cook up my own patch?
Would take a few more days till I can get at it.
BTW does anyone have knowledge how to enable IR receiver code for the smsxxx devices?
Looks like its just the matter of setting sms_board_gpio_cfg.ir to the "right" value
- which value?
Richard
next prev parent reply other threads:[~2010-06-01 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100530145240.GA21559@linux-m68k.org>
2010-05-30 15:24 ` schedule inside spin_lock_irqsave? Jiri Slaby
2010-05-30 15:32 ` Jiri Slaby
2010-06-01 17:17 ` Richard Zidlicky [this message]
2010-06-06 12:43 ` [PATCH 2.6.34] schedule inside spin_lock_irqsave Richard Zidlicky
2010-06-06 17:51 ` Jiri Slaby
2010-06-07 13:00 ` Richard Zidlicky
2010-07-06 12:40 ` Mauro Carvalho Chehab
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=20100601171710.GA5176@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/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