Message ID | 20211019155509.1018130-1-martin.kepplinger@puri.sm (mailing list archive) |
---|---|
Headers |
Received: from vger.kernel.org ([23.128.96.18]) by www.linuxtv.org with esmtp (Exim 4.92) (envelope-from <linux-media-owner@vger.kernel.org>) id 1mcrTL-009FeD-0x; Tue, 19 Oct 2021 15:56:15 +0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233146AbhJSP60 (ORCPT <rfc822;mkrufky@linuxtv.org> + 1 other); Tue, 19 Oct 2021 11:58:26 -0400 Received: from comms.puri.sm ([159.203.221.185]:33228 "EHLO comms.puri.sm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231235AbhJSP6Z (ORCPT <rfc822;linux-media@vger.kernel.org>); Tue, 19 Oct 2021 11:58:25 -0400 Received: from localhost (localhost [127.0.0.1]) by comms.puri.sm (Postfix) with ESMTP id 5CA0FDF72A; Tue, 19 Oct 2021 08:55:42 -0700 (PDT) Received: from comms.puri.sm ([127.0.0.1]) by localhost (comms.puri.sm [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eC9GdzDQKGp; Tue, 19 Oct 2021 08:55:41 -0700 (PDT) From: Martin Kepplinger <martin.kepplinger@puri.sm> To: sakari.ailus@linux.intel.com Cc: kernel@puri.sm, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, lkp@intel.com, martin.kepplinger@puri.sm, mchehab@kernel.org, paul.kocialkowski@bootlin.com Subject: [PATCH v3 0/2] media: hi846: minor build fixes Date: Tue, 19 Oct 2021 17:55:07 +0200 Message-Id: <20211019155509.1018130-1-martin.kepplinger@puri.sm> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: <linux-media.vger.kernel.org> X-Mailing-List: linux-media@vger.kernel.org X-LSpam-Score: -3.1 (---) X-LSpam-Report: No, score=-3.1 required=5.0 tests=BAYES_00=-1.9,HEADER_FROM_DIFFERENT_DOMAINS=0.5,MAILING_LIST_MULTI=-1,RCVD_IN_DNSWL_LOW=-0.7 autolearn=ham autolearn_force=no |
Series |
media: hi846: minor build fixes
|
|
Message
Martin Kepplinger
Oct. 19, 2021, 3:55 p.m. UTC
Similar to many other drivers this basically should fix the build warning where the const struct of_device_id we define can be unused. Reported here: https://lore.kernel.org/linux-media/202110170632.b6umsB8m-lkp@intel.com/ revision history ---------------- v3: (thank you Sakari) * include property.h instead of of_graph.h and remove the of_match_ptr macro v2 and v1: https://lore.kernel.org/linux-media/20211018095859.255912-1-martin.kepplinger@puri.sm/ Martin Kepplinger (2): media: hi846: include property.h instead of of_graph.h media: hi846: remove the of_match_ptr macro drivers/media/i2c/hi846.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Comments
On Tue, Oct 19, 2021 at 05:55:07PM +0200, Martin Kepplinger wrote: > Similar to many other drivers this basically should fix the build warning > where the const struct of_device_id we define can be unused. Reported > here: > https://lore.kernel.org/linux-media/202110170632.b6umsB8m-lkp@intel.com/ Thanks, Martin!>
Am Mittwoch, dem 20.10.2021 um 15:57 +0300 schrieb Sakari Ailus: > On Tue, Oct 19, 2021 at 05:55:07PM +0200, Martin Kepplinger wrote: > > Similar to many other drivers this basically should fix the build > > warning > > where the const struct of_device_id we define can be unused. > > Reported > > here: > > https://lore.kernel.org/linux-media/202110170632.b6umsB8m-lkp@intel.com/ > > Thanks, Martin!> > since the Intel test robot just reminded me that the issue still remains: are these patches queued somewhere already? thanks! martin
Hi Martin, On Thu, Nov 04, 2021 at 11:53:08AM +0100, Martin Kepplinger wrote: > Am Mittwoch, dem 20.10.2021 um 15:57 +0300 schrieb Sakari Ailus: > > On Tue, Oct 19, 2021 at 05:55:07PM +0200, Martin Kepplinger wrote: > > > Similar to many other drivers this basically should fix the build > > > warning > > > where the const struct of_device_id we define can be unused. > > > Reported > > > here: > > > https://lore.kernel.org/linux-media/202110170632.b6umsB8m-lkp@intel.com/ > > > > Thanks, Martin!> > > > > since the Intel test robot just reminded me that the issue still > remains: are these patches queued somewhere already? Not yet. And thanks for the ping. I had forgotten about these fixes and wrote a fix for the same issue, so I'm taking these two instead.