linux-kernel - Re: Re: Re: [GIT PULL] extcon for Linux 3.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <1354000869-26589-1-git-send-email-myungjoo.ham@samsung.com>
Date:	Tue, 27 Nov 2012 16:21:09 +0900
From:	MyungJoo Ham <myungjoo.ham@...sung.com>
To:	gregkh@...uxfoundation.org
Cc:	linux-kernel@...r.kernel.org, myungjoo.ham@...il.com,
	cw00.choi@...sung.com, kyungmin.park@...sung.com,
	sachin.kamat@...aro.org, khoroshilov@...ras.ru
Subject: Re: Re: Re: [GIT PULL] extcon for Linux 3.8


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> On Tue, Nov 27, 2012 at 12:54:30AM +0000, MyungJoo Ham wrote:
> > > On Thu, Nov 22, 2012 at 01:51:10PM +0900, MyungJoo Ham wrote:
> > > > Please pull extcon patches for Linux 3.8.
> > > 
> > > This is not a signed-tag pull request, which I thought I asked for
> > > previously.
> > > 
> > > Please create that, so that I can properly know I am getting the right
> > > pull request and patches.
> > 
> > A singed tag, "pull_req_20121122", has been already attached at the HEAD
> > of for-next branch.
> > 
> > Would it be more readable if the request is made with
> > git://git.kernel.org/pub/scm/linux/kernel/git/mzx/extcon.git tags/pull_req_20121122
> > rather than
> > git://git.kernel.org/pub/scm/linux/kernel/git/mzx/extcon.git for-next
> > ? (both point to the same commit and I tried the first URL for git request-pull; however git request-pull gives me the second URL as the result)
> 
> git request-pull should show you the proper tag, if you are using a new
> version of git (i.e. something fairly recent.)  What version of git are
> you using?  How did you create the signed tag?
> 
> thanks,
> 
> greg k-h

I'm using 1.7.5.4. 

And are you talking about the git update of
"682853e68 request-pull: really favor a matching tag"?

The process I did for creating request-pull message was:

$ git tag -U D606808A pull_req_20121122 HEAD
$ git push --tags
$ git request-pull f4a75d2eb7b1e2206094b901be09adb31ba63681 git:/git.kernel.org:/pub/scm/linux/kernel/git/mzx/extcon tags/pull_req_20121122 HEAD

Anyway, with the version 1.7.9.5, it produces messages with proper tag ids.


The following changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681:

  Linux 3.7-rc6 (2012-11-16 17:42:40 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/mzx/extcon tags/pull_req_20121122

----------------------------------------------------------------
extcon pull request targetting Linux 3.8 for Greg KH on 2012.11.22
This is based on Linux 3.7 rc6

----------------------------------------------------------------
Alexey Khoroshilov (1):
      extcon: arizona: unlock mutex on error path in arizona_micdet()

Chanwoo Choi (1):
      extcon: Add missing header file to extcon.h

MyungJoo Ham (1):
      extcon: kernel_doc style fix

Sachin Kamat (9):
      extcon: Fix return value in extcon-class.c
      extcon: max8997: Fix incorrect error check and return value
      extcon: max77693: Fix incorrect error check and return value
      extcon: max77693: Fix coding style
      extcon: max8997: Fix checkpatch error
      extcon: max8997: Fix a typo
      extcon: max8997: Use devm_kzalloc
      extcon: max77693: Use devm_kzalloc
      extcon: max77693: Fix uninitialised variable warning

 drivers/extcon/extcon-arizona.c  |    1 +
 drivers/extcon/extcon-class.c    |    2 +-
 drivers/extcon/extcon-max77693.c |   36 ++++++++++++---------------
 drivers/extcon/extcon-max8997.c  |   28 +++++++++------------
 include/linux/extcon.h           |   50 +++++++++++++++++++------------------
 5 files changed, 56 insertions(+), 61 deletions(-)


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJQtGkcAAoJEBOhurvWBoCK2EAP/1Hp3nKFCaNbqy7e1yg+bovM
aSDSr+0XajZOuF+Cx8yE+2DtaRBEwu7vXyzMOek9daxGBAiLOHu+FyDTa5D67p8J
eO031IHkg+Lx6JHip3csRQoyflTDc1pKnAMEKBPBPbVIqErw4q+d0WWfbQQ70z0g
Pb3iM+pLb5sIvgbdJBMRsZ1JQFgHj1Fy558s9uaCQtlh2fw6zRuj5yi8nMAzxU8c
DfSa0I2ESYeDfj+n5EoUdF3LmGeeSsrgWX4v9EtDCmzCGroddLA8BlmeTXhr32oI
9Kb7VmsUnUDtizQ59WYyiyku3NMa64LPdfqy3wlAJYbQxPJrg2AOlFzwOIbL1uLj
0ix5iq9k2I2bri2fHznpvbFnl/TAX8xiXGh5gfY10Vr4Z45HRFLf55usvAnwW137
I7FH/pkOd+YOBYiO0gIsj5ay7vpHLk9ezE9oXpUe2k9bSYXR3SAfd1cjNeAVQE1g
4nq68c6Mk3kU5COyUfoUIu8k62BnyKsWYzsI6bEfBzN1sfB3Q4fxGP+FVaAEYv80
1VwdiNeUKiDE7RTq5aBr9mXJFwoHwoZ4iuSyaQewyyZEveia9SSpp1KgvSZTAIc/
8ibW/oVYbz+US0CHzCllLBApjNrDKy/vywFfY4R5R/oxbospKICdogu/hZwbcHw3
1WF9ehMD7PW4HIrcM2hT
=ytmK
-----END PGP SIGNATURE-----
--
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/