linux-kernel - Re: [PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ

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:	Mon, 19 Jan 2015 23:54:48 -0800
From:	Tristan Lelong <tristan@...ong.xyz>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	oleg.drokin@...el.com, andreas.dilger@...el.com, askb23@...il.com,
	john.hammond@...el.com, gdonald@...il.com, anhlq2110@...il.com,
	fabio.falzoi84@...il.com, oort10@...il.com, agimenez@...valve.es,
	rupran@...server.de, surya.seetharaman9@...il.com,
	Julia.Lawall@...6.fr, joe@...ches.com, a.terekhov@...il.com,
	liang.zhen@...el.com, vthakkar1994@...il.com, amk@...y.com,
	srikrishanmalik@...il.com, rd@...ekdostal.com, bergwolf@...il.com,
	dan.carpenter@...cle.com, paul.gortmaker@...driver.com,
	tapaswenipathak@...il.com, email@...istophjaeger.info,
	uja.ornl@...il.com, brilliantov@...ox.ru, dmitry.eremin@...el.com,
	HPDD-discuss@...ts.01.org, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS
 macros

Greg,

On Sun, Jan 18, 2015 at 04:02:22PM +0900, Greg KH wrote:
> On Sat, Jan 17, 2015 at 10:41:44PM -0800, Tristan Lelong wrote:
> > Hi Greg,
> > 
> > On Sat, Jan 17, 2015 at 03:28:27PM -0800, Greg KH wrote:
> > > 
> > > I took your v2 version, please send me the difference as this is a
> > > mess...
> > 
> > Not sure I understand what you meant here. 
> > Do you want me to submit a new patch that contains only the differences between v2 and v3?
> 
> Yes please.  Make it against the tree you got the email saying when your
> v2 patch was accepted.
> 

Just for reference, I submitted this patch as a new patch "[PATCH] staging: lustre: remove kmalloc from fld_proc_hash_seq_write"
I figured out it might trigger some more comments, and didn't want to add to the confusion.
Let me know if this is the right way, or if you would prefer an answer to email with the updated patch.

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