linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.ml.walleij-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linus Walleij
	<linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Subject: Re: [PATCH 1/1] MFD: Add U300 AB3100 core support v4
Date: Thu, 21 May 2009 21:29:46 +0200	[thread overview]
Message-ID: <63386a3d0905211229t2c02109cp6213b201e451cd74@mail.gmail.com> (raw)
In-Reply-To: <20090520222012.GB4541-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>

2009/5/21 Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>:

>> +static irqreturn_t ab3100_irq_handler(int irq, void *data)
>> +{
> struct ab3100 *ab3100 = (struct ab3100 *)data;
>
> you're even passing the ab3100 pointer to request_irq, so it's all set
> already.

Yeah and all the code was actually the way you wanted it before I started
to try to separate local accesses to the struct from accesses coming
in from the outside using a singleton pattern.

But no problem, I'll fix it back in the way you want it, just a minute!

Linus Walleij

      parent reply	other threads:[~2009-05-21 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  9:17 [PATCH 1/1] MFD: Add U300 AB3100 core support v4 Linus Walleij
     [not found] ` <63386a3d0905200217i56accf6fw4ef2f8ed1793e44-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-20 22:20   ` Samuel Ortiz
     [not found]     ` <20090520222012.GB4541-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2009-05-21 19:29       ` Linus Walleij [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=63386a3d0905211229t2c02109cp6213b201e451cd74@mail.gmail.com \
    --to=linus.ml.walleij-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).