Hi Masahiro > > When I applied this, I added the following fix-up. > > > > diff --git a/scripts/kconfig/.gitignore b/scripts/kconfig/.gitignore > index 54266f3..0aabc1d 100644 > --- a/scripts/kconfig/.gitignore > +++ b/scripts/kconfig/.gitignore > @@ -2,7 +2,6 @@ > # Generated files > # > *.moc > -*.mo > > # > # configuration programs > > > > > .mo is no longer generated. > > It was added by > commit c26dd719a5b9d94d12211f2d101bd7dffb7f9f1f > > > > Please double-check if it is OK. I left it as I was not sure where the .mo extension came from. And trying out the different frontends did not generate any .mo files (I tried with a kernel before my patches). So I assume the .mo extension was added because it is often seen in combination with .pot files, and not because the kernel actually generated such file. See https://make.wordpress.org/polyglots/handbook/glossary/#mo-files for a short description of the .mo files. In other words - the fixup is correct. Thanks! Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
