From: Ingo Molnar <mingo@elte.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, lethal@linux-sh.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] Free setup_irq() interrupt V2
Date: Tue, 10 Mar 2009 16:33:32 +0100 [thread overview]
Message-ID: <20090310153332.GB23463@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0903101615540.29264@localhost.localdomain>
* Thomas Gleixner <tglx@linutronix.de> wrote:
> On Tue, 10 Mar 2009, Ingo Molnar wrote:
> > * Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > > Magnus,
> > >
> > > On Tue, 10 Mar 2009, Magnus Damm wrote:
> > > > From: Magnus Damm <damm@igel.co.jp>
> > > > This patch adds a __free_irq() function for releasing
> > > > interrupts requested with setup_irq().
> > >
> > > I think there is a simpler solution than adding yet another
> > > function for the confusion of driver writers. See below.
> >
> > Uhm, i asked for that solution ;-)
>
> Uhm, I missed that :)
>
> > To reduce the confusion in generic code with yet another IRQF flag.
>
> Hmm. I still prefer a solution which confuses the few people hacking
> on kernel/irq/* instead of having another function which confuses the
> already confused driver writers.
>
> I can live with the two functions as well, but then please let us use
> a function name which is more intuitive than __free_irq().
>
> setup_irq() -> remove_irq()
> request_irq() -> free_irq()
Sure, that's fine with me.
I almost suggested shutdown_irq() to Magnus originally, then
went for __free_irq().
Ingo
next prev parent reply other threads:[~2009-03-10 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 10:24 Magnus Damm
2009-03-10 12:41 ` Ingo Molnar
2009-03-10 14:26 ` Thomas Gleixner
2009-03-10 15:04 ` Ingo Molnar
2009-03-10 15:26 ` Thomas Gleixner
2009-03-10 15:33 ` Ingo Molnar [this message]
2009-03-11 2:32 ` Magnus Damm
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=20090310153332.GB23463@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®