From: Greg KH <gregkh@linuxfoundation.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: broonie@opensource.wolfsonmicro.com, thomas.abraham@linaro.org,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
jonghwa3.lee@samsung.com, linux-kernel@vger.kernel.org,
"sameo@linux.intel.com" <sameo@linux.intel.com>
Subject: Re: [PATCH 0/2] mfd: MAX8997: Support irq domain for Maxim MAX8997
Date: Thu, 10 May 2012 16:52:37 -0700 [thread overview]
Message-ID: <20120510235237.GA28601@kroah.com> (raw)
In-Reply-To: <4FAC5313.80909@samsung.com>
On Fri, May 11, 2012 at 08:45:23AM +0900, Chanwoo Choi wrote:
> On 05/11/2012 03:20 AM, Greg KH wrote:
>
> > On Thu, May 10, 2012 at 07:54:48PM +0900, Chanwoo Choi wrote:
> >> This patchset add support irq domain for Maxim MAX8997 interrupts.
> >>
> >> The first patch is based on patch written by Thomas Abraham and fix
> >> two bug which set max8997->irq_domain instead of NULL pointer and
> >> correct wrong parameter by Chanwoo Choi.
> >> - https://lkml.org/lkml/2012/4/18/145
> >> The second patch use irq domain for MAX8997 muic interrupt instead
> >> of irq_base in platform data of MAX8997 driver.
> >>
> >> But, I posted following patchset related to MAX8997 driver.
> >> This patchset support Extcon framework in extcon-max8997 driver to
> >> control external connector instead of max8997-muic driver. So, first
> >> patch add MAX8997 extcon driver(drivers/extcon/extcon-max8997.c) and
> >> last patch remove old MAX8997 muic driver(drivers/misc/max8997-muic.c).
> >> - https://lkml.org/lkml/2012/5/8/98
> >>
> >> This patchset was applied in below git repository of Greg Kroah-Hartman.
> >> - http://git.kernel.org/?p=linux/kernel/git/gregkh/driver-core.git;a=shortlog;h=refs/heads/driver-core-next
> >>
> >> I think that this patchset should be applied on the git repository
> >> of Greg Kroah-Hartman to remove possible conflict issue when merged.
> >
> > That's fine with me, should the MFD maintainer have been copied on this
> > to get his signed-off-by on it?
> >
>
> I knew that first patch written by Thomas Abraham has been already
> confirmed ack message from MFD maintainer(Samuel Ortiz
> <sameo@linux.intel.com>). You can check it on first patch and below git
> repository of Mark Brown.
Ok, but why didn't you cc: him and everyone else who acked and
signed-off on that patch?
> The below patch has occurred build break, so it was reverted by Mark
> Brown. And then I did post this patchset with bug fix.
>
> http://git.kernel.org/?p=linux/kernel/git/broonie/regulator.git;a=commit;h=98d8618af37728f6e18e84110ddb99987b47dd12
So does that mean this one is ok, but the older one isn't?
confused, what exactly should I do here?
greg k-h
next prev parent reply other threads:[~2012-05-10 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 10:54 [PATCH 0/2] mfd: MAX8997: Support irq domain for Maxim MAX8997 Chanwoo Choi
2012-05-10 18:20 ` Greg KH
2012-05-10 23:45 ` Chanwoo Choi
2012-05-10 23:52 ` Greg KH [this message]
2012-05-11 0:38 ` Chanwoo Choi
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 1:10 Chanwoo Choi
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=20120510235237.GA28601@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=jonghwa3.lee@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sameo@linux.intel.com \
--cc=thomas.abraham@linaro.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 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.