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] [day] [month] [year] [list]
Date:	Tue, 03 Jun 2014 09:26:00 +0900
From:	Chanwoo Choi <cw00.choi@...sung.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [GIT PULL] extcon next-v2 for v3.16

On 06/03/2014 09:12 AM, Greg KH wrote:
> On Tue, Jun 03, 2014 at 08:53:42AM +0900, Chanwoo Choi wrote:
>> Dear Greg,
>>
>> On 06/03/2014 07:55 AM, Greg KH wrote:
>>> On Mon, Jun 02, 2014 at 02:09:16PM +0900, Chanwoo Choi wrote:
>>>> Dear Greg,
>>>>
>>>> This is extcon-next-v2 full request for v3.16. This pull request includes
>>>> additional patchset after merged previous extcon-next pull request(tags/extcon-next-for-v3.16).
>>>> I add detailed description of this pull request on below. Please pull extcon with following update.
>>>>
>>>> Best Regards,
>>>> Chanwoo Choi
>>>>
>>>> The following changes since commit 3f79a3fb5f41e8f2229e5bf8aa725eaa79686f14:
>>>>
>>>>   extcon: palmas: Use devm_extcon_dev_allocate for extcon_dev (2014-04-29 09:52:12 +0900)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-v2-for-3.16
>>>
>>> I was thinking it was too late for 3.16-rc1, as the merge window is now
>>> open and I like to have things in my tree a week or so before that
>>> happens, but I figured this was nice and self-contained so I would take
>>> it.
>>
>> Sorry late pull-request. I'll send next pull-request before -rc7 release certainly.
>>
>>>
>>> So I pulled, and built, and then got this:
>>>
>>> ERROR: "regmap_irq_get_virq" [drivers/extcon/extcon-sm5502.ko] undefined!
>>> ERROR: "regmap_add_irq_chip" [drivers/extcon/extcon-sm5502.ko] undefined!
>>> ERROR: "regmap_del_irq_chip" [drivers/extcon/extcon-sm5502.ko] undefined!
>>>
>>> which makes me know that you haven't done much build testing of the code
>>> :(
>>
>> Sorry about this mistake. As you comment, I'll check much build testing.
> 
> Any reason your trees are not in linux-next?  I'd recommend them to be
> there, so you can get that build testing ahead-of-time.

As you comment, I'm going to find the way to include extcon patchset for build test
in linux-next.

Best Regards,
Chanwoo Choi











--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ