linux-kernel - Re: [PATCH] doc: fix some typos in documentations

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1380623046.14430.10.camel@jlt4.sipsolutions.net>
Date:	Tue, 01 Oct 2013 12:24:06 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Xishi Qiu <qiuxishi@...wei.com>
Cc:	rob@...dley.net, Andrew Morton <akpm@...ux-foundation.org>,
	linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-wireless@...r.kernel.org
Subject: Re: [PATCH] doc: fix some typos in documentations

On Wed, 2013-09-18 at 11:45 +0800, Xishi Qiu wrote:
>  
>  to ensure the driver cannot be built-in when rfkill is modular. The !RFKILL
> -case allows the driver to be built when rfkill is not configured, which which
> +case allows the driver to be built when rfkill is not configured, which
>  case all rfkill API can still be used but will be provided by static inlines
>  which compile to almost nothing.

It looks like this was intended to say "in which" instead of the "which
which" you remove, rather than just "which".

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/