linux-kernel - Re: [PATCH 49/50] mars: generic pre-patch for mars

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:	Wed, 2 Jul 2014 09:36:21 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Thomas Schoebel-Theuer <tst@...oebel-theuer.de>
Cc:	linux-kernel@...r.kernel.org,
	Thomas Schöbel-Theuer <tst@...d1.de>
Subject: Re: [PATCH 49/50] mars: generic pre-patch for mars

On Wed, Jul 02, 2014 at 11:02:09AM +0200, Thomas Schoebel-Theuer wrote:
> > Maintaining out of tree code is not our problem, sorry. thanks, greg k-h 
> 
> OK, I just noticed that in the meantime many vfs_*() are present now
> which were missing when I started the project on very old kernels (or
> maybe I missed something, sorry for any potential mistakes).
> 
> So I will happily make a new version which has the lowest possible
> footprint in the kernel, but nevertheless is _internally_ portable (just
> for me and the needs of 1&1 users).
> 
> This will incur many changes in many places in the patchset. Is it OK to
> re-submit the _whole_ patchset again after that?

Given that your patchset really isn't even in a reviewable format (you
just add one file per-patch) resending it doesn't bother anyone :)

Hint, you will have to work on a better way to submit this code in a
format that is mergable.  It's a non-trivial task, but going to be
required if you wish for this to ever be accepted.

Best of luck,

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/