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
| ||
|
Date: Tue, 23 Oct 2018 13:32:16 +0200 From: Geert Uytterhoeven <geert@...ux-m68k.org> To: Marc Zyngier <marc.zyngier@....com> Cc: Bartosz Golaszewski <brgl@...ev.pl>, Sekhar Nori <nsekhar@...com>, Kevin Hilman <khilman@...nel.org>, David Lechner <david@...hnology.com>, Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Arnd Bergmann <arnd@...db.de>, Greg KH <gregkh@...uxfoundation.org>, Mark Rutland <mark.rutland@....com>, Yoshinori Sato <ysato@...rs.sourceforge.jp>, Rich Felker <dalias@...c.org>, Andy Shevchenko <andy.shevchenko@...il.com>, "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>, Peter Rosin <peda@...ntia.se>, Jiri Slaby <jslaby@...e.com>, Thomas Gleixner <tglx@...utronix.de>, Daniel Lezcano <daniel.lezcano@...aro.org>, Magnus Damm <magnus.damm@...il.com>, Johan Hovold <johan@...nel.org>, Rob Herring <robh+dt@...nel.org>, Frank Rowand <frowand.list@...il.com>, Philippe Ombredanne <pombredanne@...b.com>, Linux ARM <linux-arm-kernel@...ts.infradead.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>, Linux-Arch <linux-arch@...r.kernel.org>, Bartosz Golaszewski <bgolaszewski@...libre.com> Subject: Re: [RESEND PATCH v3 3/3] sh: add the sh_ prefix to early platform symbols Hi Marc, On Tue, Oct 23, 2018 at 1:11 PM Marc Zyngier <marc.zyngier@....com> wrote: > On Mon, 27 Aug 2018 10:06:51 +0100, > Bartosz Golaszewski <brgl@...ev.pl> wrote: > As for the whole "early device" debate, my take is that we'd be much > better off making the device model available early, rather than trying > to architect something that is simply papering over the issue. The device model itself can be made available earlier, but the big blocker is mainly the use of everything related to the scheduler (threads, msleep()), which depends on the "early" timer. I think it can be made to work if msleep() and all thread-related functions would return -EPROBE_DEFER, but that should be handled in every single driver, which may be already the case for thread-related functions, but not for e.g. msleep(), which currently returns void. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Powered by blists - more mailing lists