public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, Julie Zhu <julie.zhu@xilinx.com>,
	linux-usb@vger.kernel.org, john.linn@xilinx.com, greg@kroah.com
Subject: Re: [PATCH] [V1] USB: Add support for Xilinx USB host controller
Date: Tue, 22 Sep 2009 09:43:16 +1000	[thread overview]
Message-ID: <1253576596.7103.166.camel@pasglop> (raw)
In-Reply-To: <20090921225612.GA32278@oksana.dev.rtsoft.ru>

On Tue, 2009-09-22 at 02:56 +0400, Anton Vorontsov wrote:
> On Tue, Sep 22, 2009 at 06:49:40AM +1000, Benjamin Herrenschmidt wrote:
> > On Mon, 2009-09-21 at 13:38 -0600, Julie Zhu wrote:
> > 
> > > +	iounmap(hcd->regs);
> > > +err_ioremap:
> > > +	irq_dispose_mapping(irq);
> > 
> > You missed that one too :-)
> > 
> > I'm actually considering making irq_dispose_mapping() a private
> > API and rename it to something like __irq_dispose_mapping() :-)
> 
> I.e. turning irq_dispose_mapping() into nop, and __-prefixed
> (private) variant would actually dispose irq mapping?
> 
> The nop part is important, because otherwise having no cleanup
> variant of an allocation/mapping routine feels odd and might raise
> questions by non-ppc people (e.g. subsystem maintainers when they
> see no cleanup path for such a call).
> 
> And if we'll want to refcount irq mappings in the future, some
> drivers will be ready without modifications, i.e. the ones that
> got irq_dispose_mapping() wrong:

Yup. I agree. I'll look into it

Ben.

      reply	other threads:[~2009-09-21 23:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 19:38 [PATCH] [V1] USB: Add support for Xilinx USB host controller Julie Zhu
2009-09-21 20:47 ` Grant Likely
2009-09-21 20:49 ` Benjamin Herrenschmidt
2009-09-21 22:56   ` Anton Vorontsov
2009-09-21 23:43     ` Benjamin Herrenschmidt [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=1253576596.7103.166.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=greg@kroah.com \
    --cc=john.linn@xilinx.com \
    --cc=julie.zhu@xilinx.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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