On 5/8/26 3:41 PM, Andrew Lunn wrote:
> On Fri, May 08, 2026 at 11:23:43AM -0600, Shuah Khan wrote:
>> On 5/8/26 10:38, Adrien Reynard wrote:
>>
>> Missing commit log
>>
>>> Signed-off-by: Adrien Reynard <[email protected]>
>>> ---
>>> Documentation/dev-tools/kasan.rst | 2 +-
>>> Documentation/networking/switchdev.rst | 2 +-
>>> Documentation/virt/uml/user_mode_linux_howto_v2.rst | 2 +-
>>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/Documentation/dev-tools/kasan.rst
>>> b/Documentation/dev-tools/kasan.rst
>>> index 4968b2aa60c8..3a8bd40ad905 100644
>>> --- a/Documentation/dev-tools/kasan.rst
>>> +++ b/Documentation/dev-tools/kasan.rst
>>> @@ -392,7 +392,7 @@ reserved to tag freed memory regions.
>>> If the hardware does not support MTE (pre ARMv8.5), Hardware Tag-Based
>>> KASAN
>>> will not be enabled. In this case, all KASAN boot parameters are ignored.
>>> -Note that enabling CONFIG_KASAN_HW_TAGS always results in in-kernel TBI
>>> being
>>> +Note that enabling CONFIG_KASAN_HW_TAGS always results in-kernel TBI being
>>
>> This is correct the way it is - no need to change this. "results in
>> in-kernel"
>>
>>> enabled. Even when ``kasan.mode=off`` is provided or when the hardware
>>> does not
>>> support MTE (but supports TBI).
>>> diff --git a/Documentation/networking/switchdev.rst
>>> b/Documentation/networking/switchdev.rst
>>> index 2966b7122f05..948bce44ca9b 100644
>>> --- a/Documentation/networking/switchdev.rst
>>> +++ b/Documentation/networking/switchdev.rst
>>> @@ -162,7 +162,7 @@ The switchdev driver can know a particular port's
>>> position in the topology by
>>> monitoring NETDEV_CHANGEUPPER notifications. For example, a port moved
>>> into a
>>> bond will see its upper master change. If that bond is moved into a
>>> bridge,
>>> the bond's upper master will change. And so on. The driver will track
>>> such
>>> -movements to know what position a port is in in the overall topology by
>>> +movements to know what position a port is in the overall topology by
>>
>> This looks fine.
>
> Fine as in the change is correct, or fine in that the original is
> correct and the change is wrong?
>
> Because the change is wrong, there should be two in's here. Please
> search the archive for an explanation why.
>
> This is the second time in a week i've had to deal with "improvements"
> like this actually breaking stuff. Which also shows that the submitter
> did not search to see if somebody has tried to fix this once already,
> and failed.
>
> Can we get the tool changed to add a warning, something like:
>
> WARNING: This tool uses very simple pattern matching to look for
> repeated words. It does not understand the complexity of English,
> and will often result in false positive reports. Please assume it is
> wrong until proven otherwise.
There was no commit log and no cover letter AFAIK.
Do we know what tool was used?
Adrien, how did you discover these repeated words?
(If it's my script from 2021, I'll gladly update it.)
--
~Randy
