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: <26s13395-1ro2-37o8-01q5-6r4p09p69174@xreary.bet>
Date: Wed, 26 Mar 2025 12:00:45 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
cc: Antheas Kapenekakis <lkml@...heas.dev>, 
    platform-driver-x86@...r.kernel.org, linux-input@...r.kernel.org, 
    LKML <linux-kernel@...r.kernel.org>, 
    Benjamin Tissoires <bentiss@...nel.org>, 
    Corentin Chary <corentin.chary@...il.com>, 
    "Luke D . Jones" <luke@...nes.dev>, Hans de Goede <hdegoede@...hat.com>
Subject: Re: [PATCH v5 09/11] HID: asus: add basic RGB support

On Wed, 26 Mar 2025, Ilpo Järvinen wrote:

> You don't need to "pause" for the merge window, in some subsystem 
> there's mandatory pause during merge window but I find that unnecessary.
> I know people on pdx86 do review during merge window so no need to wait 
> when working with patches related to pdx86. Just don't expect patches 
> get applied during the merge window or right after it (the latter tends to 
> be the most busiest time of cycle for me) :-).
> 
> It's more about the frequency, how often to send a series which is 
> relatively large. Large number of versions end up just filling inboxes 
> (and patchwork's pending patches list) and we don't have time to read them 
> all through so I suggest waiting like 3 days at minimum between versions 
> when the series is large or complex to give time to go through the series.
> 
> This is not a hard rule, so if there are e.g. many significant changes, 
> feel free to "violate" it in that case.

Exactly. I am unlikely to do much review during the merge window myself, 
but I'll pick up the patchset and followup once the merge window is over, 
so feel free to keep discussing and polishing it with me on CC :)

Thanks,

-- 
Jiri Kosina
SUSE Labs


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ