Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
Date:   Wed, 19 Jul 2023 18:22:32 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From:   "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
Message-ID: <58d0c47502218fd689c5ecd100ba0d5d02d89926@linux.dev>
TLS-Required: No
Subject: Re: [PATCH v7 5/5] mfd: tps6586x: register restart handler
To:     "Benjamin Bara" <bbara93@gmail.com>, dmitry.osipenko@collabora.com,
        konstantin@linuxfoundation.org
Cc:     bbara93@gmail.com, benjamin.bara@skidata.com, jonathanh@nvidia.com,
        lee@kernel.org, linux-i2c@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
        peterz@infradead.org, rafael.j.wysocki@intel.com,
        richard.leitner@linux.dev, treding@nvidia.com,
        wsa+renesas@sang-engineering.com, wsa@kernel.org
In-Reply-To: <20230719082251.3501424-1-bbara93@gmail.com>
References: <20230719082251.3501424-1-bbara93@gmail.com>
 <215679f1-a866-1e92-1bab-9c80918927a6@collabora.com>
Precedence: bulk

July 19, 2023 at 4:22 AM, "Benjamin Bara" <bbara93@gmail.com> wrote:=20
>=20@Konstantin:
> Do you think it makes sense to print a warning when adding "non-standar=
d
> trailers" during running "b4 trailers -u", maybe around the
> find_trailers() checks? I could provide a RFC, if considered useful.

With b4 being used for other projects than just the Linux kernel, I don't=
 think it makes sense for us to track what is a valid and what is an inva=
lid "person-trailer". I know that we could make it configurable, but I do=
n't think this will actually improve the situation.

One goal for b4 is to allow defining validation tests and requiring them =
prior to "b4 send", so I think this is a better mechanism for dealing wit=
h such situations.

-K