linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org, kyungmin.park@samsung.com,
	cw00.choi@samsung.com, myungjoo.ham@gmail.com
Subject: Re: [GIT PULL] extcon fixes for Linux 3.7
Date: Mon, 22 Oct 2012 12:56:06 -0700	[thread overview]
Message-ID: <20121022195606.GA13640@kroah.com> (raw)
In-Reply-To: <1350878680-12164-1-git-send-email-myungjoo.ham@samsung.com>

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

  reply	other threads:[~2012-10-22 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  4:04 [GIT PULL] extcon fixes for Linux 3.7 MyungJoo Ham
2012-10-22 19:56 ` Greg KH [this message]
2012-10-23  8:18   ` [GIT PULL v2] " MyungJoo Ham
2012-10-24  2:41     ` 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=20121022195606.GA13640@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@gmail.com \
    --cc=myungjoo.ham@samsung.com \
    /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).