All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org,
	Samuel Ortiz <sameo@linux.intel.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>,
	Donggeun Kim <dg77.kim@samsung.com>,
	myungjoo.ham@gmail.com
Subject: Re: [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header.
Date: Wed, 29 Jun 2011 22:28:10 -0700	[thread overview]
Message-ID: <20110630052808.GA796@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1309397507-24959-3-git-send-email-myungjoo.ham@samsung.com>

On Thu, Jun 30, 2011 at 10:31:47AM +0900, MyungJoo Ham wrote:
> IRQ definitions are needed to be accessed by board support package codes
> as well. Because they are not only used by MAX8997 MFD device drivers,
> this patch pulls such definitions out of private header, which is meant
> for MAX8997 MFD device drivers.

Why is this needed?

  reply	other threads:[~2011-06-30  5:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  1:31 [PATCH 1/3] MFD: MAX8997: IRQ Handling Bugfix MyungJoo Ham
2011-06-30  1:31 ` [PATCH 2/3] MFD: MAX8997: Support Wake-up from Suspend MyungJoo Ham
2011-06-30  1:31 ` [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header MyungJoo Ham
2011-06-30  5:28   ` Mark Brown [this message]
2011-06-30  5:56     ` MyungJoo Ham
2011-06-30  5:57       ` Mark Brown
2011-06-30  8:00         ` MyungJoo Ham
2011-06-30 15:56           ` Mark Brown
2011-07-01  0:43             ` MyungJoo Ham
2011-07-04 17:16               ` Mark Brown
2011-07-05  5:57                 ` MyungJoo Ham
2011-07-05  6:19                   ` Mark Brown
2011-07-05  6:49                     ` MyungJoo Ham
2011-07-05 19:53                       ` Mark Brown

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=20110630052808.GA796@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=dg77.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=myungjoo.ham@gmail.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=sameo@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.