[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121022195606.GA13640@kroah.com>
Date: Mon, 22 Oct 2012 12:56:06 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: MyungJoo Ham <myungjoo.ham@...sung.com>
Cc: linux-kernel@...r.kernel.org, kyungmin.park@...sung.com,
cw00.choi@...sung.com, myungjoo.ham@...il.com
Subject: Re: [GIT PULL] extcon fixes for Linux 3.7
On Mon, Oct 22, 2012 at 01:04:40PM +0900, MyungJoo Ham wrote:
> Hello Greg,
>
>
> The following changes since commit 6f0c0580b70c89094b3422ba81118c7b959c7556:
>
> Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/mzx/extcon.git for-next
This isn't a signed-tag to pull from, it looks just like a branch
instead. Is it really a signed tag? If so, it sure didn't work like
one.
> Axel Lin (4):
> extcon: adc-jack: Fix checking return value of request_any_context_irq
> extcon: adc-jack: Add missing MODULE_LICENSE
> extcon: Fix kerneldoc for extcon_set_cable_state and extcon_set_cable_state_
> extcon: max77693: Use max77693_update_reg for rmw operations
>
> Chanwoo Choi (1):
> extcon: MAX77693: Add platform data for MUIC device to initialize registers
>
> Devendra Naga (1):
> extcon-max8997: remove usage of ret in max8997_muic_handle_charger_type_detach
>
> Jenny TC (1):
> extcon : register for cable interest by cable name
>
> Peter Huewe (2):
> extcon: Unregister compat class at module unload to fix oops
> extcon: unregister compat link on cleanup
>
> Sachin Kamat (2):
> extcon: Remove duplicate inclusion of extcon.h header file
> extcon: Fix return value in extcon_register_interest()
>
> anish kumar (5):
> extcon: standard cable names definition and declaration changed
> extcon: optimising the check_mutually_exclusive function
> extcon: checkpatch warning removal
Why is a checkpatch cleanup for 3.7? Shouldn't that wait for 3.8?
Care to redo this?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists