[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mST6rfJDVGGT2+=_FUCXwms6N8mo2eoLzQ6KW64M9BtQ@mail.gmail.com>
Date: Wed, 11 May 2022 17:29:33 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Mickaël Salaün <mic@...ikod.net>,
Brian Norris <briannorris@...omium.org>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Andy Whitcroft <apw@...onical.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
"Jason A . Donenfeld" <Jason@...c4.com>,
Joe Perches <joe@...ches.com>,
Kees Cook <keescook@...omium.org>,
Konstantin Meskhidze <konstantin.meskhidze@...wei.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Paul Moore <paul@...l-moore.com>, Tom Rix <trix@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>, llvm@...ts.linux.dev
Subject: Re: [PATCH v2 0/5] Fix clang-format configuration according to checkpatch.pl
Hi Mickaël,
On Wed, May 11, 2022 at 4:19 PM Mickaël Salaün <mic@...ikod.net> wrote:
>
> Miguel, what do you think about this series? Do you plan to take it for
> the next merge window? FYI, I plan to use it for Landlock [1] and send
> it for the next merge window. Could you publish your pending
> clang-format changes so that I can make sure everything is OK?
It looked good to me overall (though it indeed conflicts with what I
was doing) -- I will take it for the next merge window. I am thinking
of putting Brian as author and you as Co-developed-by for the last one
to be fair (Brian: is this OK with you too?). Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists