On Fri, Jan 7, 2022 at 11:29 AM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > On Fri, Jan 7, 2022 at 11:25 AM Andy Shevchenko > <andy.shevchenko@xxxxxxxxx> wrote: > > On Fri, Jan 7, 2022 at 12:12 PM Stafford Horne <shorne@xxxxxxxxx> wrote: > > > On Fri, Jan 07, 2022 at 10:36:12AM +0100, Geert Uytterhoeven wrote: > > > > On Thu, Jan 6, 2022 at 11:50 PM Gabriel L. Somlo <gsomlo@xxxxxxxxx> wrote: > > > > ... > > > > > > Many (most?) blurbs do mention the module name. > > > > > > I was doubting this as well, but I searched and its true. The text 'module will > > > be called' shows up many times, there is also different text. > > > > > > $ grep -r 'module will be called' drivers/ | wc > > > 1347 9023 9086 > > > > > > $ grep -r 'tristate \"' drivers/ | wc > > > 7169 47486 521795 > > > > Just a side note: `git grep ...` is much faster in the Git trees. > > Indeed. > > > And for this particular case I dare to advertise a script I wrote [1] > > to help with recursive searches. > > > > [1]: https://github.com/andy-shev/home-bin-tools/blob/master/gl4func.sh > > Cool! > > My fingers are used to type > > git grep -w <pat1> -- $(git grep -lw <pat2> -- ...) > > ;-) Actually you can just use git grep --and? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx 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
