linux-kernel - Re: [PATCH v12 01/19] input: cyapa: modify code to following kernel code style

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]

Date:	Thu, 4 Dec 2014 09:32:12 -0800
From:	"dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>
To:	Dudley Du <dudl@...ress.com>
Cc:	Jeremiah Mahler <jmmahler@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v12 01/19] input: cyapa: modify code to following kernel
 code style

Dudley, Jeremiah,

On Thu, Dec 04, 2014 at 05:54:43AM +0000, Dudley Du wrote:
> Jeremiah,
> 
> I didn't submitted this fix patch, but Dmitry has been helping apply the fix patch quickly, maybe todoay or tommorrow.

The patches that I apply for the next merge window should appear first
in my 'next' branch in

	git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git

and then in the linux-next and eventually in mainline.

> 
> For the pathces that I made were worked based off of kernel mainline.

I resolved the conflicts and applied this 1/19 patch, next time you are
re-posting the series could you please base them off my 'next' branch?
It will help me applhy them much more easily.

Thanks!

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