From: Greg KH <gregkh@linuxfoundation.org>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: "Mark Brown" <broonie@opensource.wolfsonmicro.com>,
"Randy Dunlap" <rdunlap@xenotime.net>,
최찬우 <cw00.choi@samsung.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH -next] extcon: extcon-arizona depends on INPUT
Date: Wed, 5 Sep 2012 17:06:03 -0700 [thread overview]
Message-ID: <20120906000603.GA7043@kroah.com> (raw)
In-Reply-To: <6721797.222311346888851339.JavaMail.weblogic@epml19>
On Wed, Sep 05, 2012 at 11:47:31PM +0000, MyungJoo Ham wrote:
> > On Wed, Sep 05, 2012 at 11:28:03AM +0800, Mark Brown wrote:
> > > On Tue, Sep 04, 2012 at 04:51:00PM -0700, Randy Dunlap wrote:
> > >
> > > > This build error still happens in linux-next of 20120904.
> > >
> > > > Can we get the patch merged for linux-next?
> > >
> > > Greg's the one managing extcon in -next.
> >
> > Yeah, can someone forward this to me so I can apply it? I can't seem to
> > find it anywhere...
> >
> > greg k-h
>
> I've been creating "extcon-for-next" tree at git.infradead.org
> I'll rebase the branch base on your driver-core-next
>
> http://git.infradead.org/users/kmpark/linux-samsung/shortlog/refs/heads/extcon-for-next
Don't worry, I've already applied this patch now.
thanks,
greg k-h
next prev parent reply other threads:[~2012-09-06 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 23:47 Re: [PATCH -next] extcon: extcon-arizona depends on INPUT MyungJoo Ham
2012-09-06 0:03 ` Mark Brown
2012-09-06 0:06 ` Greg KH [this message]
2012-09-06 3:24 ` anish singh
2012-09-06 3:39 ` Greg KH
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=20120906000603.GA7043@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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