From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
"linux-media@vger.kernel.org >> Linux Media Mailing List"
<linux-media@vger.kernel.org>
Subject: Re: [PATCH 1/8] [media] em28xx: fix em28xx-input removal
Date: Sun, 21 Dec 2014 20:18:43 +0100 [thread overview]
Message-ID: <54971D13.7090508@googlemail.com> (raw)
In-Reply-To: <20141220145119.GH11285@n2100.arm.linux.org.uk>
Am 20.12.2014 um 15:51 schrieb Russell King - ARM Linux:
> On Sat, Dec 20, 2014 at 03:11:54PM +0100, Frank Schäfer wrote:
>> Hi Russel,
> I guess you won't mind if I mis-spell your name too...
Wow... it seems to be very easy to offend you...
Sorry, that was definitely not my intention. I did not do this on purpose.
It was just a simple mistake and I will try to avoid it in the future.
>
>> I'd prefer to keep the button initialization related stuff together in
>> em28xx_init_buttons() and do the cancel_delayed_work_sync() only if we
>> have buttons (dev->num_button_polling_addresses).
>> That's how we already do it with the IR work struct (see
>> em28xx_ir_suspend()).
> Provided all places that touch buttons_query_work are properly updated
> that's fine, but to me that is fragile and asking for trouble. It's far
> better to ensure that everything is properly initialised so you don't
> have to remember to conditionalise every single reference to a work
> struct.
>
> In any case, delayed work struct initialisation is cheap - it doesn't
> involve any additional memory, it only initialises the various members
> of the struct (and the lockdep information for the static key) so there
> really is no argument against always initialising delayed works or normal
> works, timers, etc to avoid these kinds of bugs.
Fair enough !
Regards,
Frank Schäfer
next prev parent reply other threads:[~2014-12-21 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 12:44 [PATCH 0/8] Fix issues in em28xx Russell King - ARM Linux
2014-12-20 12:45 ` [PATCH 1/8] [media] em28xx: fix em28xx-input removal Russell King
[not found] ` <549583AA.9040204@googlemail.com>
2014-12-20 14:51 ` Russell King - ARM Linux
2014-12-21 19:18 ` Frank Schäfer [this message]
2014-12-20 12:45 ` [PATCH 2/8] [media] em28xx: ensure "closing" messages terminate with a newline Russell King
2014-12-20 12:45 ` [PATCH 3/8] [media] em28xx-input: fix missing newlines Russell King
2014-12-20 12:45 ` [PATCH 4/8] [media] em28xx-core: " Russell King
2014-12-20 12:45 ` [PATCH 5/8] [media] em28xx-audio: " Russell King
2014-12-20 12:45 ` [PATCH 6/8] " Russell King
2014-12-20 12:45 ` [PATCH 7/8] [media] em28xx-dvb: " Russell King
2014-12-20 12:45 ` [PATCH 8/8] [media] em28xx-video: " Russell King
2014-12-20 14:10 ` [PATCH 0/8] Fix issues in em28xx Frank Schäfer
2014-12-20 14:53 ` Russell King - ARM Linux
2014-12-21 19:20 ` Frank Schäfer
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=54971D13.7090508@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mchehab@osg.samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.