linux-kernel - Re: [PATCH v2 4/9] staging: panel: Use defined value or checking module params state

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: <CAOMZO5D4gSQGdQwJZq4y-7CfUbz=ZTsrDDvmHZX136jFpHK67w@mail.gmail.com>
Date:	Thu, 27 Nov 2014 19:10:40 -0200
From:	Fabio Estevam <festevam@...il.com>
To:	Willy Tarreau <w@....eu>
Cc:	Mariusz Gorski <marius.gorski@...il.com>,
	devel@...verdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 4/9] staging: panel: Use defined value or checking
 module params state

On Thu, Nov 27, 2014 at 7:05 PM, Willy Tarreau <w@....eu> wrote:

> Mariusz, for people who have to parse hundreds to thousands of e-mails
> a day, dealing with non-trivial operation modes like this is never easy.
>
> I think (I'll let Greg suggest what he prefers) that the most reliable
> thing to do *right now* is to rebase your tree on top of Greg's staging
> tree, and you send the resulting series (what you apply *after* staging)

Actually 'staging-testing' branch would be better:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/log/?h=staging-testing&ofs=100

There are 4 patches from Mariusz already applied there.
--
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/