On Thu, Jan 23, 2025 at 10:25:20AM +0200, Khaled Elnaggar wrote: > diff --git a/Documentation/networking/can.rst b/Documentation/networking/can.rst > index 62519d38c58b..b018ce346392 100644 > --- a/Documentation/networking/can.rst > +++ b/Documentation/networking/can.rst > @@ -699,10 +699,10 @@ RAW socket option CAN_RAW_JOIN_FILTERS > > The CAN_RAW socket can set multiple CAN identifier specific filters that > lead to multiple filters in the af_can.c filter processing. These filters > -are indenpendent from each other which leads to logical OR'ed filters when > +are independent from each other which leads to logical OR'ed filters when > applied (see :ref:`socketcan-rawfilter`). > > -This socket option joines the given CAN filters in the way that only CAN > +This socket option joins the given CAN filters in the way that only CAN > frames are passed to user space that matched *all* given CAN filters. The > semantic for the applied filters is therefore changed to a logical AND. > > diff --git a/Documentation/networking/napi.rst b/Documentation/networking/napi.rst > index 6083210ab2a4..f970a2be271a 100644 > --- a/Documentation/networking/napi.rst > +++ b/Documentation/networking/napi.rst > @@ -362,7 +362,7 @@ It is expected that ``irq-suspend-timeout`` will be set to a value much larger > than ``gro_flush_timeout`` as ``irq-suspend-timeout`` should suspend IRQs for > the duration of one userland processing cycle. > > -While it is not stricly necessary to use ``napi_defer_hard_irqs`` and > +While it is not strictly necessary to use ``napi_defer_hard_irqs`` and > ``gro_flush_timeout`` to use IRQ suspension, their use is strongly > recommended. > Looks OK, thanks! Reviewed-by: Bagas Sanjaya <bagasdotme@xxxxxxxxx> -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
