public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
Cc: "Hans J. Koch" <hjk@linutronix.de>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"lethal@linux-sh.org" <lethal@linux-sh.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] uio: uio_pdrv_genirq V2
Date: Thu, 10 Jul 2008 15:49:46 +0200	[thread overview]
Message-ID: <20080710134946.GC3202@local> (raw)
In-Reply-To: <20080710110631.GA582@digi.com>

On Thu, Jul 10, 2008 at 01:06:31PM +0200, Uwe Kleine-König wrote:
> Hi,
> 
> Hans J. Koch wrote:
> > > > +       ret = uio_register_device(&pdev->dev, priv->uioinfo);
> > > > +       if (ret) {
> > > > +               dev_err(&pdev->dev, "unable to register uio device\n");
> > > > +               goto bad1;
> > > > +       }
> > > > +
> > > > +       platform_set_drvdata(pdev, priv);
> > > This should probably go before uio_register_device.  (Uups, this is an
> > > issue for uio_pdrv, too.)
> > 
> > Yes, because uio_register_device will enable the irq, and you might
> > arrive in the handler without having your platform data in place.
> How do we want to fix that?  Should I sent a new version that also
> includes the memory-leak fix and copyright specification?  Or another
> incremental patch?

Send another incremental patch for uio_pdrv, just for the records.
I'll sort it out with Greg later, if he finds many small patches
annoying, I can easily combine them.

Thanks,
Hans


  reply	other threads:[~2008-07-10 13:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  3:52 [PATCH] uio: uio_pdrv_genirq V2 Magnus Damm
2008-07-10  6:56 ` Uwe Kleine-König
2008-07-10  8:46   ` Alan Cox
2008-07-10 10:30     ` Uwe Kleine-König
2008-07-10 10:02       ` Alan Cox
2008-07-10 10:47         ` Uwe Kleine-König
2008-07-11  6:15       ` Magnus Damm
2008-07-10 10:58   ` Hans J. Koch
2008-07-10 11:06     ` Uwe Kleine-König
2008-07-10 13:49       ` Hans J. Koch [this message]
2008-07-11  8:45     ` Magnus Damm
2008-07-11  9:00       ` Uwe Kleine-König

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=20080710134946.GC3202@local \
    --to=hjk@linutronix.de \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --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