From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Clang-Built-Linux ML <clang-built-linux@googlegroups.com>,
Joe Perches <joe@perches.com>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust to clang-version.sh removal
Date: Sat, 23 Jan 2021 12:20:51 +0300 [thread overview]
Message-ID: <20210123092051.GT2696@kadam> (raw)
In-Reply-To: <CA+icZUXxJnhXwiFAJ+f23xWLq-t6ZmF6X_wJPNaEoCVqjP4N=A@mail.gmail.com>
In networking then they want you to say which tree it applies to, but
it's not as simple as saying "net" vs "net-next". If it's a bugfix then
you should write that against "net" but if it's a clean up or a fix to a
recent change then it should be written against "net-next".
Also linux-next is not necessarily the same thing as net-next.
Networking patches should be written against either net or net-next, not
linux-next.
BPF tried to implement similar rules to they're not big enough to impose
their own rules. It's quite a big headache to try to figure out which
tree to use if you're like me and have no clue about bpf.
Anyway, the point of the net vs net-next is that devs are supposed to
figure out the exact tree and they're supposed to only write net-next if
it doesn't apply to net.
It's not clear to me the value of putting linux-next in the subject.
Doesn't everyone develop against the latest devel tree? Certainly I
can't imagine any maintainers doing extra work to try figure out the
date of the linux-next release. Surely, they just say "Doesn't apply to
foo-tree. Resend if necessary." That's the fastest and easiest
response when patches don't apply.
regards,
dan carpente
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Clang-Built-Linux ML <clang-built-linux@googlegroups.com>,
Joe Perches <joe@perches.com>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust to clang-version.sh removal
Date: Sat, 23 Jan 2021 09:20:51 +0000 [thread overview]
Message-ID: <20210123092051.GT2696@kadam> (raw)
In-Reply-To: <CA+icZUXxJnhXwiFAJ+f23xWLq-t6ZmF6X_wJPNaEoCVqjP4N=A@mail.gmail.com>
In networking then they want you to say which tree it applies to, but
it's not as simple as saying "net" vs "net-next". If it's a bugfix then
you should write that against "net" but if it's a clean up or a fix to a
recent change then it should be written against "net-next".
Also linux-next is not necessarily the same thing as net-next.
Networking patches should be written against either net or net-next, not
linux-next.
BPF tried to implement similar rules to they're not big enough to impose
their own rules. It's quite a big headache to try to figure out which
tree to use if you're like me and have no clue about bpf.
Anyway, the point of the net vs net-next is that devs are supposed to
figure out the exact tree and they're supposed to only write net-next if
it doesn't apply to net.
It's not clear to me the value of putting linux-next in the subject.
Doesn't everyone develop against the latest devel tree? Certainly I
can't imagine any maintainers doing extra work to try figure out the
date of the linux-next release. Surely, they just say "Doesn't apply to
foo-tree. Resend if necessary." That's the fastest and easiest
response when patches don't apply.
regards,
dan carpente
next prev parent reply other threads:[~2021-01-23 9:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 16:01 [PATCH] MAINTAINERS: adjust to clang-version.sh removal Lukas Bulwahn
2021-01-21 16:01 ` Lukas Bulwahn
2021-01-21 16:15 ` Sedat Dilek
2021-01-21 16:15 ` Sedat Dilek
2021-01-21 16:22 ` Lukas Bulwahn
2021-01-21 16:22 ` Lukas Bulwahn
2021-01-22 12:33 ` Dan Carpenter
2021-01-22 12:33 ` Dan Carpenter
2021-01-23 2:38 ` Sedat Dilek
2021-01-23 2:38 ` Sedat Dilek
2021-01-23 9:20 ` Dan Carpenter [this message]
2021-01-23 9:20 ` Dan Carpenter
2021-01-21 16:16 ` Nathan Chancellor
2021-01-21 16:16 ` Nathan Chancellor
2021-01-21 16:20 ` Sedat Dilek
2021-01-21 16:20 ` Sedat Dilek
2021-01-21 16:25 ` Lukas Bulwahn
2021-01-21 16:25 ` Lukas Bulwahn
2021-01-21 17:26 ` Masahiro Yamada
2021-01-21 17:26 ` Masahiro Yamada
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=20210123092051.GT2696@kadam \
--to=dan.carpenter@oracle.com \
--cc=clang-built-linux@googlegroups.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=pia.eichinger@st.oth-regensburg.de \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=sedat.dilek@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.