linux-kernel - Re: [PATCH] Staging: ced1401: fix coding style in ced

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: <20140113224101.GA17837@kroah.com>
Date:	Mon, 13 Jan 2014 14:41:01 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Pol Eyschen <poleyschen@...il.com>
Cc:	Dan Carpenter <dan.carpenter@...cle.com>,
	Mark Einon <mark@...on.net>, devel@...verdev.osuosl.org,
	jack@...e.cz, sachin.kamat@...aro.org,
	linux-kernel@...r.kernel.org, ufimtseva@...il.com
Subject: Re: [PATCH] Staging: ced1401: fix coding style in ced_ioc.c

On Mon, Jan 13, 2014 at 11:31:29PM +0100, Pol Eyschen wrote:
> 
> On 13.01.2014, at 22:44, Dan Carpenter wrote:
> 
> > On Mon, Jan 13, 2014 at 09:35:53PM +0000, Mark Einon wrote:
> >> On Mon, Jan 13, 2014 at 08:41:40PM +0100, Pol Eyschen wrote:
> >>> From: Pol Eyschen <poleyschen@...mail.com>
> >>> 
> >>> All comments fixed to match the kernel coding style.
> >>> 
> >>> Signed-off-by: Pol Eyschen <poleyschen@...il.com>
> >>> ---
> >> 
> >> This patch doesn't apply to my staging-next branch. Are you making your
> >> changes to the staging-next branch of
> >> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git?
> >> 
> 
> I cloned
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git and
> made my changes to that branch.

That is Linus's tree, not "linux-next" which we all develop against.

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/