From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Greg KH <gregkh@linuxfoundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [PATCH -next] extcon: extcon-arizona depends on INPUT
Date: Wed, 5 Sep 2012 11:28:03 +0800 [thread overview]
Message-ID: <20120905032802.GB5076@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <504693E4.8050808@xenotime.net>
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.
next prev parent reply other threads:[~2012-09-05 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 7:28 linux-next: Tree for Aug 24 Stephen Rothwell
2012-08-24 17:04 ` [PATCH -next] extcon: extcon-arizona depends on INPUT Randy Dunlap
2012-08-26 23:53 ` Chanwoo Choi
2012-09-04 23:51 ` Randy Dunlap
2012-09-05 3:28 ` Mark Brown [this message]
2012-09-05 19:16 ` Greg KH
2012-09-05 20:18 ` Randy Dunlap
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=20120905032802.GB5076@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).