linux-kernel - Re: [PATCH 0/5] reset: make non-modular drivers really non modular

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, 24 Oct 2016 10:56:45 +0200
From:   Philipp Zabel <p.zabel@...gutronix.de>
To:     Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:     linux-kernel@...r.kernel.org,
        Antoine Tenart <antoine.tenart@...e-electrons.com>,
        Joachim Eastwood <manabian@...il.com>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Maxime Ripard <maxime.ripard@...e-electrons.com>,
        Michal Simek <michal.simek@...inx.com>,
        Moritz Fischer <moritz.fischer@...us.com>,
        Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
        Sören Brinkmann <soren.brinkmann@...inx.com>,
        Steffen Trumtrar <s.trumtrar@...gutronix.de>
Subject: Re: [PATCH 0/5] reset: make non-modular drivers really non modular

Hi Paul,

Am Samstag, den 22.10.2016, 17:48 -0400 schrieb Paul Gortmaker:
> [[PATCH 0/5] reset: make non-modular drivers really non modular] On 13/06/2016 (Mon 14:03) Paul Gortmaker wrote:
> 
> > For anyone new to the underlying goal of this cleanup, we are trying to
> > not use module support for code that can never be built as a module since:
> 
> Hi Philipp,
> 
> I sent this several months ago, and aside from a couple Ack'd by, there
> was no negative feedback or similar.
> 
> Since then there have been two more drivers added with the same issue.
> 
> 	reset-make-ath79-explicitly-non-modular.patch
> 	reset-pistachio-make-it-explicitly-non-modular.patch
> 
> Should I assume that the original send has fallen through the cracks and
> resend with the two new patches, or do you still have the original five
> in a queue somewhere?

thanks for the reminder. I had them stashed away because I wanted to see
whether the introduction of per-driver Kconfig options would change some
of them to become modular. That wasn't the case, so I have pushed your
patches to the reset/next branch now, with fixed up commit messages.

> I'd like to merge as many of these as I can via their respective
> maintainers vs. trying to send them to Linus directly.
> 
> Thanks,
> Paul.

regards
Philipp