lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 16 Jan 2020 10:40:30 +0100 From: Jean Delvare <jdelvare@...e.de> To: Luca Ceresoli <luca@...aceresoli.net> Cc: linux-doc@...r.kernel.org, linux-i2c@...r.kernel.org, Wolfram Sang <wsa@...-dreams.de>, Peter Rosin <peda@...ntia.se>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 05/26] docs: i2c: fix typo On Sun, 5 Jan 2020 23:49:51 +0100, Luca Ceresoli wrote: > Fix "issus" -> "issues". > > Signed-off-by: Luca Ceresoli <luca@...aceresoli.net> > Acked-by: Peter Rosin <peda@...ntia.se> > --- > Documentation/i2c/i2c-topology.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/i2c/i2c-topology.rst b/Documentation/i2c/i2c-topology.rst > index 0875090d6aeb..b413ef6a6773 100644 > --- a/Documentation/i2c/i2c-topology.rst > +++ b/Documentation/i2c/i2c-topology.rst > @@ -169,7 +169,7 @@ PL1. If you build a topology with a parent-locked mux being the child > of another mux, this might break a possible assumption from the > child mux that the root adapter is unused between its select op > and the actual transfer (e.g. if the child mux is auto-closing > - and the parent mux issus I2C-transfers as part of its select). > + and the parent mux issues I2C-transfers as part of its select). > This is especially the case if the parent mux is mux-locked, but > it may also happen if the parent mux is parent-locked. > Reviewed-by: Jean Delvare <jdelvare@...e.de> -- Jean Delvare SUSE L3 Support
Powered by blists - more mailing lists