public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tomáš Janoušek" <tomi@nomi.cz>
To: Alessandro Zummo <alessandro.zummo@towertech.it>
Cc: linux-kernel@vger.kernel.org, David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH] rtc-dev: stop periodic interrupts on device release
Date: Sat, 26 Jul 2008 20:06:10 +0200	[thread overview]
Message-ID: <20080726180610.GA12168@nomi.cz> (raw)
In-Reply-To: <20080726195521.36d4d48c@i1501.lan.towertech.it>

Hello,

On Sat, Jul 26, 2008 at 07:55:21PM +0200, Alessandro Zummo wrote:
>  I'm not sure this is appropriate. sometimes the PIE is used to control
>  external hardware and it doesn't make sense to have an application that's
>  always open to handle that. 
> 
>  Any app should be responsible to release what it has allocated, if appropriate,
>  and not rely on someone else to do on his behalf.

mplayer and aireplay-ng have never done so. And what about crashes? Am I
supposed to create a small "rtcpieoff" applications and make it into all
distributions so that everyone can clean up the mess?

Additionally, it has been a regression against the old rtc and drivers like
rtc-sh do so even today.

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

  reply	other threads:[~2008-07-26 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 15:46 [PATCH] rtc-dev: stop periodic interrupts on device release Tomas Janousek
2008-07-26 17:55 ` Alessandro Zummo
2008-07-26 18:06   ` Tomáš Janoušek [this message]
2008-07-26 18:13     ` Alessandro Zummo
2008-07-26 19:58       ` David Brownell
2008-07-26 20:50 ` David Brownell
2008-07-27  3:03   ` Mike Frysinger
2008-07-27  5:03     ` David Brownell
2008-07-28 20:41   ` Tomáš Janoušek
2008-07-28 20:47     ` Alessandro Zummo
2008-07-28 22:05     ` David Brownell
2008-07-28 23:36       ` Tomáš Janoušek
2008-07-29 20:08         ` David Brownell

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=20080726180610.GA12168@nomi.cz \
    --to=tomi@nomi.cz \
    --cc=alessandro.zummo@towertech.it \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@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