Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3E997C2BA4C for ; Wed, 26 Jan 2022 15:00:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242438AbiAZPAP (ORCPT ); Wed, 26 Jan 2022 10:00:15 -0500 Received: from smtp-out2.suse.de ([195.135.220.29]:34858 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242482AbiAZPAP (ORCPT ); Wed, 26 Jan 2022 10:00:15 -0500 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 259A51F3B0; Wed, 26 Jan 2022 15:00:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1643209214; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rwbYZgvLVZEk/ivTRJgPJiqAFyuLTxzp6dsl+egvEqk=; b=CESMnfmY2f3upUqCDTFX6TNnK+K1Q7QmKdrfkGM8PkaIksuADNYw+54IucNkl82I6EfUcH lUG49v3F1EJCykgGHb1Bk1O+3oz+Gz/p2dHJD9KZk4qgEPLXpOj4nJ9qDNdZmUzhj/hiU4 tmZavISOrpiYGjmcf/m6mAaJr1ew5fI= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1643209214; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rwbYZgvLVZEk/ivTRJgPJiqAFyuLTxzp6dsl+egvEqk=; b=qIAWgYZQCt7Neteo+4IWTSKChII0fwMCvL3J4vFeZ2wtu2QZ8skNWqdMLOD2MCcZM8rmfs WTBlJCTPdGYmCqBQ== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id 128AEA3B81; Wed, 26 Jan 2022 15:00:14 +0000 (UTC) Date: Wed, 26 Jan 2022 16:00:14 +0100 Message-ID: From: Takashi Iwai To: Mark Brown Cc: Jaroslav Kysela , Takashi Iwai , Shuah Khan , alsa-devel@alsa-project.org, linux-kselftest@vger.kernel.org, Shuah Khan Subject: Re: [PATCH v2] kselftest: alsa: Add test case for writing invalid values In-Reply-To: <20220125162824.3816659-1-broonie@kernel.org> References: <20220125162824.3816659-1-broonie@kernel.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Tue, 25 Jan 2022 17:28:24 +0100, Mark Brown wrote: > > Attempt to write various invalid values for control types we know about and > check that something sensible happens. The ABI isn't quite as clearly > defined as one might like, rather than generating an error when an invalid > value is written many devices will silently rewrite the value into one that > is valid for the control. The exact value chosen is not predictable so in > the case the write succeeds we just check that the value we read back is > one that is valid for the control. > > Reviewed-by: Shuah Khan > Signed-off-by: Mark Brown > --- > > v2: > - Fix a couple of _integer()/_integer64() confusions. Thanks, applied now to for-next branch. Takashi