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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 14 May 2022 09:31:23 -0700 From: Joe Perches <joe@...ches.com> To: Jonathan Cameron <jic23@...nel.org>, Yury Norov <yury.norov@...il.com> Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, David Laight <David.Laight@...LAB.COM>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Julia Lawall <Julia.Lawall@...ia.fr>, Michał Mirosław <mirq-linux@...e.qmqm.pl>, Nicholas Piggin <npiggin@...il.com>, Nicolas Palix <nicolas.palix@...g.fr>, Peter Zijlstra <peterz@...radead.org>, Rasmus Villemoes <linux@...musvillemoes.dk>, Matti Vaittinen <Matti.Vaittinen@...rohmeurope.com>, linux-kernel@...r.kernel.org, Lars-Peter Clausen <lars@...afoo.de>, Michael Hennerich <Michael.Hennerich@...log.com>, linux-iio@...r.kernel.org Subject: Re: [PATCH 05/22] iio: replace bitmap_weight with bitmap_weitght_{eq,le} where appropriate On Sat, 2022-05-14 at 16:53 +0100, Jonathan Cameron wrote: > On Tue, 10 May 2022 08:47:33 -0700 > Yury Norov <yury.norov@...il.com> wrote: > > > bitmap_weight_{eq,le} is better than bitmap_weight because it > > may return earlier. > > > > CC: Jonathan Cameron <jic23@...nel.org> > > CC: Lars-Peter Clausen <lars@...afoo.de> > > CC: Michael Hennerich <Michael.Hennerich@...log.com> > > CC: linux-iio@...r.kernel.org > > CC: linux-kernel@...r.kernel.org > > Signed-off-by: Yury Norov <yury.norov@...il.com> > without being cc'd on the cover letter, there is no obvious way for > me to know this is reliant in some series to be found in next. > > Please call out the exact dependency and whilst it's a long list, > it is good to cc all people cc'd on individual patches also > on the cover letter so they have that background information. When doing a treewide change like this, vger would commonly reject the message because of too many recipients. > > Change seems fine, but I've no idea when/if to pick it up because of > that lack of information. You could try using lore with the in-reply-to message header id https://lore.kernel.org/lkml/20220510154750.212913-6-yury.norov@gmail.com/ that gives you the entire thread.
Powered by blists - more mailing lists