From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 582F0C433DB for ; Tue, 2 Feb 2021 19:43:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 214E764E08 for ; Tue, 2 Feb 2021 19:43:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239895AbhBBTnI (ORCPT ); Tue, 2 Feb 2021 14:43:08 -0500 Received: from 8bytes.org ([81.169.241.247]:54002 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233291AbhBBNxt (ORCPT ); Tue, 2 Feb 2021 08:53:49 -0500 Received: by theia.8bytes.org (Postfix, from userid 1000) id 2451B3E6; Tue, 2 Feb 2021 14:53:07 +0100 (CET) Date: Tue, 2 Feb 2021 14:53:05 +0100 From: Joerg Roedel To: Lu Baolu Cc: iommu@lists.linux-foundation.org, Yian Chen , Ashok Raj , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/3] iommu/vt-d: Parse SATC reporting structure Message-ID: <20210202135305.GW32671@8bytes.org> References: <20210202044057.615277-1-baolu.lu@linux.intel.com> <20210202044057.615277-3-baolu.lu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210202044057.615277-3-baolu.lu@linux.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 02, 2021 at 12:40:56PM +0800, Lu Baolu wrote: > + case ACPI_DMAR_TYPE_SATC: > + satc = container_of(header, struct acpi_dmar_satc, header); > + pr_info("SATC flags: 0x%x\n", satc->flags); > + break; Did the pr_info() slip through or is there a real purpose for having this information in the kernel log?