From: "Mickaël Salaün" <mic@digikod.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Brian Norris <briannorris@chromium.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Joe Perches <joe@perches.com>, Kees Cook <keescook@chromium.org>,
Konstantin Meskhidze <konstantin.meskhidze@huawei.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Paul Moore <paul@paul-moore.com>, Tom Rix <trix@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH v2 0/5] Fix clang-format configuration according to checkpatch.pl
Date: Wed, 11 May 2022 19:40:25 +0200 [thread overview]
Message-ID: <9c5eb09f-8f7d-2339-c8bb-4b908d7abab0@digikod.net> (raw)
In-Reply-To: <CANiq72mST6rfJDVGGT2+=_FUCXwms6N8mo2eoLzQ6KW64M9BtQ@mail.gmail.com>
On 11/05/2022 17:29, Miguel Ojeda wrote:
> Hi Mickaël,
>
> On Wed, May 11, 2022 at 4:19 PM Mickaël Salaün <mic@digikod.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.
Good. Please keep me in the loop, I would like to try your changes as
soon as possible (before you make a PR).
> 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?).
Looks fair.
next prev parent reply other threads:[~2022-05-11 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 16:01 Mickaël Salaün
2022-05-06 16:01 ` [PATCH v2 1/5] clang-format: Update and extend the for_each list with tools/ Mickaël Salaün
2022-05-20 11:57 ` Miguel Ojeda
2022-05-06 16:01 ` [PATCH v2 2/5] clang-format: Update to clang-format >= 6 Mickaël Salaün
2022-05-06 16:01 ` [PATCH v2 3/5] clang-format: Fix goto labels indentation Mickaël Salaün
2022-05-20 17:07 ` Miguel Ojeda
2022-05-06 16:01 ` [PATCH v2 4/5] clang-format: Fix empty curly braces Mickaël Salaün
2022-05-20 17:15 ` Miguel Ojeda
2022-05-20 17:24 ` Joe Perches
2022-05-20 17:50 ` Miguel Ojeda
2022-05-20 18:00 ` Joe Perches
2022-05-20 18:57 ` Miguel Ojeda
2022-05-23 11:14 ` Mickaël Salaün
2022-05-06 16:01 ` [PATCH v2 5/5] clang-format: Fix space after for_each macros Mickaël Salaün
2022-05-11 15:40 ` Joe Perches
2022-05-11 17:34 ` Mickaël Salaün
2022-05-11 17:38 ` Joe Perches
2022-05-11 14:19 ` [PATCH v2 0/5] Fix clang-format configuration according to checkpatch.pl Mickaël Salaün
2022-05-11 15:29 ` Miguel Ojeda
2022-05-11 17:38 ` Brian Norris
2022-05-11 17:40 ` Mickaël Salaün [this message]
2022-05-20 19:11 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c5eb09f-8f7d-2339-c8bb-4b908d7abab0@digikod.net \
--to=mic@digikod.net \
--cc=Jason@zx2c4.com \
--cc=apw@canonical.com \
--cc=briannorris@chromium.org \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lukas.bulwahn@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®