Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9336810rwd; Wed, 21 Jun 2023 06:16:52 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7fcxrOZO/nRrmp3L8DVytkZRGt6clAXGd6NCK3ZIFZCXpctJMW0rKQ1XMGuR+PZmhhGWkG X-Received: by 2002:a17:90b:e12:b0:24b:52cb:9a31 with SMTP id ge18-20020a17090b0e1200b0024b52cb9a31mr28233057pjb.22.1687353412509; Wed, 21 Jun 2023 06:16:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687353412; cv=none; d=google.com; s=arc-20160816; b=lrc25/az87I2g3k1ZCU659R3WJl603Lvk0Iqr5GEocd13t9fR/2aA3qMmWD8tMo0dQ iW6w7vNYkAgD+sAHg+XGO9+p9j6ljvaxCOh7DHtXX82uwlHOS7E5usAFJeBY+2JFe5a5 YDazb+13yhpbNfrjzBrhErMMAB3miAxjWb6KQkxKVlF6pCxEGqBUmD0W3bivKl8yR0BK CCmK9HVfl4D9oLz/VwoeouOb3vmm4aq8LOa48iKKWSwsG4aJuG8NS+x7DDlPBihEUPFw nu6pnF4RhFyeHJy9j3jwZ5ZFiy5tXC5M4CaeBZlUDcVQzahW/PcEM+TPxO+/ItU/b7NI SEYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=oOqnsf4JTgard+CNqhYgPXINKh7Q8qdMJU5633e+nBM=; b=wpqPLY50kHPzalO6yVBf11QjcwBhvJGXC7TeKhqHApgLy62QoW18U69s8iOI1m8GDh Xqsr+3VBNeuw6AmtszCOC5Fy9w+1w9gxm1ucQhp6oE7vr5ZNvRp0AwKbO0avjeq9IxwK LARZ3OSEpurhylUTZ8umz38wNK6PDNV45t3YHw27NrtTBkbitmSN6wzWhjch8HPLZIL4 wtoFKkk8LXrP1kYwTP8jjvYiMlae4Tlz3eVmCJvjx7cq31inHBfvYR08KfHwS5yIilLx n5wTX95ZEQ88HvEmlAOoQH3vQ8gIJYKdAWNeVXRDHywlR4t02g4iu2KvpuekENdTqaa4 N2rA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=fwQOjPd7; dkim=neutral (no key) header.i=@suse.cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id lh15-20020a170903290f00b001aafec82436si3824434plb.204.2023.06.21.06.16.37; Wed, 21 Jun 2023 06:16:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=fwQOjPd7; dkim=neutral (no key) header.i=@suse.cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231927AbjFUMqo (ORCPT + 99 others); Wed, 21 Jun 2023 08:46:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59238 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229602AbjFUMqn (ORCPT ); Wed, 21 Jun 2023 08:46:43 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 66553107; Wed, 21 Jun 2023 05:46:42 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 205E021AC4; Wed, 21 Jun 2023 12:46:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1687351601; 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=oOqnsf4JTgard+CNqhYgPXINKh7Q8qdMJU5633e+nBM=; b=fwQOjPd7/G+CpK9ni1W7ie3R5W+7mrZgm5GSbpleKmGfQD0en8W0BziBVElKa5NEgnuVxC I0D/Kv5yDFG57YktGlcGZCVw41iZ9R4N4IlVz/thOu1hwi5Xurc4cxw50z8OsGo0ecX6Au KWAFDulYQV19/fIVyHy+aydRk2Ab9VM= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1687351601; 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=oOqnsf4JTgard+CNqhYgPXINKh7Q8qdMJU5633e+nBM=; b=CCcofopDQJy5eNfLe407xe6vbI1vbG7gSAcZclZaag5nMt8A2dbS5JaUJUSLluBGObdi87 QGRIM2L9rJqZckDA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id F135E133E6; Wed, 21 Jun 2023 12:46:40 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id pRkNODDxkmS/UwAAMHmgww (envelope-from ); Wed, 21 Jun 2023 12:46:40 +0000 Date: Wed, 21 Jun 2023 14:47:43 +0200 From: Cyril Hrubis To: Damien Le Moal Cc: kernel test robot , Niklas Cassel , lkp@intel.com, "Martin K. Petersen" , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Linux Memory Management List , Hannes Reinecke , oe-lkp@lists.linux.dev, Christoph Hellwig , ltp@lists.linux.it Subject: Re: [LTP] [linux-next:master] [scsi] eca2040972: ltp.ioprio_set03.fail Message-ID: References: <202306192248.1ece4c29-oliver.sang@intel.com> <61f22c1d-6b04-d193-57c9-8cad1c555e4b@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61f22c1d-6b04-d193-57c9-8cad1c555e4b@kernel.org> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > kernel test robot noticed "ltp.ioprio_set03.fail" on: > > LTP maintainers, > > Patches have been submitted to fix this issue. Were these patches applied ? Looks like they are in, at least these two: ioprio: use ioprio.h kernel header if it exists ioprio: Use IOPRIO_PRIO_NUM to check prio range And there does not seem to be anything ioprio related haning in the LTP patchwork. -- Cyril Hrubis chrubis@suse.cz