On Thu, Sep 06, 2012 at 08:54:16AM +0530, anish singh wrote:
> On Thu, Sep 6, 2012 at 5:36 AM, Greg KH wrote:
> > On Wed, Sep 05, 2012 at 11:47:31PM +, 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,
On Thu, Sep 6, 2012 at 5:36 AM, Greg KH wrote:
> On Wed, Sep 05, 2012 at 11:47:31PM +, 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
On Wed, Sep 05, 2012 at 11:47:31PM +, 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
On Wed, Sep 05, 2012 at 11:47:31PM +, MyungJoo Ham wrote:
> > On Wed, Sep 05, 2012 at 11:28:03AM +0800, Mark Brown wrote:
> > Yeah, can someone forward this to me so I can apply it? I can't seem to
> > find it anywhere...
> I've been creating "extcon-for-next" tree at git.infradead.org
>
> 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
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
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
On Wed, Sep 05, 2012 at 11:47:31PM +, MyungJoo Ham wrote:
On Wed, Sep 05, 2012 at 11:28:03AM +0800, Mark Brown wrote:
Yeah, can someone forward this to me so I can apply it? I can't seem to
find it anywhere...
I've been creating extcon-for-next tree at git.infradead.org
I'll rebase
On Wed, Sep 05, 2012 at 11:47:31PM +, 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
On Thu, Sep 6, 2012 at 5:36 AM, Greg KH gre...@linuxfoundation.org wrote:
On Wed, Sep 05, 2012 at 11:47:31PM +, 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
On Thu, Sep 06, 2012 at 08:54:16AM +0530, anish singh wrote:
On Thu, Sep 6, 2012 at 5:36 AM, Greg KH gre...@linuxfoundation.org wrote:
On Wed, Sep 05, 2012 at 11:47:31PM +, MyungJoo Ham wrote:
On Wed, Sep 05, 2012 at 11:28:03AM +0800, Mark Brown wrote:
On Tue, Sep 04, 2012 at
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
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On 08/26/2012 04:53 PM, Chanwoo Choi wrote:
> On 08/25/2012 02:04 AM, Randy Dunlap wrote:
>
>> From: Randy Dunlap
>>
>> extcon-arizona uses input_*() functions so it should depend
>> on INPUT.
>>
>> ERROR: "input_event" [drivers/extcon/extcon-arizona.ko] undefined!
>> ERROR: "input_free_device"
On 08/26/2012 04:53 PM, Chanwoo Choi wrote:
On 08/25/2012 02:04 AM, Randy Dunlap wrote:
From: Randy Dunlap rdun...@xenotime.net
extcon-arizona uses input_*() functions so it should depend
on INPUT.
ERROR: input_event [drivers/extcon/extcon-arizona.ko] undefined!
ERROR: input_free_device
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.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
On 08/25/2012 02:04 AM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> extcon-arizona uses input_*() functions so it should depend
> on INPUT.
>
> ERROR: "input_event" [drivers/extcon/extcon-arizona.ko] undefined!
> ERROR: "input_free_device" [drivers/extcon/extcon-arizona.ko] undefined!
>
On 08/25/2012 02:04 AM, Randy Dunlap wrote:
From: Randy Dunlap rdun...@xenotime.net
extcon-arizona uses input_*() functions so it should depend
on INPUT.
ERROR: input_event [drivers/extcon/extcon-arizona.ko] undefined!
ERROR: input_free_device [drivers/extcon/extcon-arizona.ko]
18 matches
Mail list logo