On Fri, Feb 10, 2023 at 12:15:15PM +0200, Andy Shevchenko wrote: > On Fri, Feb 10, 2023 at 12:48 AM Asmaa Mnebhi <asmaa@xxxxxxxxxx> wrote: > > First of all, do not top-post! > > > Thank you for your response. I was just going to contact you regarding this. I successfully sent these patches to you, Linus and Bartosz while they failed to get delivered to the "*.kernel.org" emails below: > > linux-gpio@xxxxxxxxxxxxxxx; > > linux-kernel@xxxxxxxxxxxxxxx; > > linux-acpi@xxxxxxxxxxxxxxx > > > > Have these emails changed? > > No, but you need to work with your company's IT to understand what's > going on. Your mails are only available privately and not in the > archives on lore.kernel.org. This is an issue and I'm not going to > comment on something that was not in public. To illustrate what I'm talking about: https://lore.kernel.org/linux-gpio/CACRpkdZ_sPCa+Q6MWUKj1ytCe5AxTp--bMmbRTUfsNO0kZTMpQ@xxxxxxxxxxxxxx/T/#t > > These patches don't have much in common with gpio-mlxbf or gpio-mlxbf2 because the hardware registers and logic have changed across generations. The only similar code between gpio-mlxbf2.c and gpio-mlxbf3.c is the irq handling. > > I see, don't forget to put it in the cover letter for the next version > (you will send it when you will be sure that emails are going to the > kernel.org archives). -- With Best Regards, Andy Shevchenko
