From: Trilok Soni <quic_tsoni@quicinc.com>
To: Christoph Hellwig <hch@infradead.org>,
John Moon <quic_johmoo@quicinc.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"Nicolas Schier" <nicolas@fjasle.eu>,
<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Arnd Bergmann" <arnd@arndb.de>,
Bjorn Andersson <andersson@kernel.org>,
Todd Kjos <tkjos@google.com>,
Matthias Maennich <maennich@google.com>,
Giuliano Procida <gprocida@google.com>, <kernel-team@android.com>,
<libabigail@sourceware.org>, Jordan Crouse <jorcrous@amazon.com>,
"Satya Durga Srinivasu Prabhala" <quic_satyap@quicinc.com>,
Elliot Berman <quic_eberman@quicinc.com>
Subject: Re: [PATCH v2 0/2] Validating UAPI backwards compatibility
Date: Fri, 10 Mar 2023 10:20:14 -0800 [thread overview]
Message-ID: <c4b39b28-1f18-c436-e3c5-b015600ca3a2@quicinc.com> (raw)
In-Reply-To: <ZArlx5wrw+ZQWUg4@infradead.org>
On 3/10/2023 12:09 AM, Christoph Hellwig wrote:
> On Tue, Feb 28, 2023 at 11:54:00PM -0800, John Moon wrote:
>> Our goal is to add tooling for vendor driver developers because the
>> upstream model of expert maintainer code review can be difficult to
>> replicate in-house. Tools may help developers catch simple UAPI
>> incompatibilities that could be easily overlooked by in-house review.
>
> Why would this matter in any way for the kernel? If you tool is useful
> for in-kernel usage it should be added to the tree and documented as
> such, but ouf of tree crap simply does not matter.
This tool will be helpful for the kernel maintainers and reviewers as
well if it can detect potential UAPI backward compatibilities. Even for
the developers while changing UAPI interfaces at kernel.org before
submission.
John is trying to highlight also that this tool can be useful for
downstream users who want to keep the UAPI backward compatibility like
we do at upstream. We can remove the above text, since we would like to
mainline it at kernel.org.
---Trilok Soni
next prev parent reply other threads:[~2023-03-10 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 7:54 John Moon
2023-03-01 7:54 ` [PATCH v2 1/2] check-uapi: Introduce check-uapi.sh John Moon
2023-03-03 21:09 ` Dodji Seketeli
2023-03-05 4:22 ` Masahiro Yamada
2023-03-05 17:08 ` John Moon
2023-03-01 7:54 ` [PATCH v2 2/2] docs: dev-tools: Add UAPI checker documentation John Moon
2023-03-05 6:20 ` Masahiro Yamada
2023-03-06 16:56 ` John Moon
2023-03-01 17:50 ` [PATCH v2 0/2] Validating UAPI backwards compatibility Nick Desaulniers
2023-03-01 18:03 ` John Moon
2023-03-01 19:24 ` John Moon
2023-03-01 22:33 ` John Moon
2023-03-01 23:33 ` Nick Desaulniers
2023-03-01 23:35 ` Trilok Soni
2023-03-01 23:52 ` Mark Wielaard
2023-03-01 23:59 ` John Moon
2023-03-10 8:09 ` Christoph Hellwig
2023-03-10 18:20 ` Trilok Soni [this message]
2023-03-20 6:26 ` Christoph Hellwig
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=c4b39b28-1f18-c436-e3c5-b015600ca3a2@quicinc.com \
--to=quic_tsoni@quicinc.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=gprocida@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jorcrous@amazon.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maennich@google.com \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=quic_eberman@quicinc.com \
--cc=quic_johmoo@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=tkjos@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).