From: Philip Li <philip.li@intel.com> To: Dan Carpenter <dan.carpenter@oracle.com> Cc: Paul Cercueil <paul@crapouillou.net>, kbuild-all@lists.01.org, kernel test robot <lkp@intel.com>, Sandy Huang <hjc@rock-chips.com>, David Airlie <airlied@linux.ie>, Philippe Cornu <philippe.cornu@st.com>, dri-devel@lists.freedesktop.org, Russell King <linux@armlinux.org.uk>, Yannick Fertre <yannick.fertre@st.com>, Tomi Valkeinen <tomi.valkeinen@ti.com>, Laurent Pinchart <laurent.pinchart@ideasonboard.com> Subject: Re: [kbuild-all] Re: [PATCH v2 2/2] drm: automatic legacy gamma support Date: Wed, 16 Dec 2020 09:06:50 +0800 [thread overview] Message-ID: <20201216010650.GA330@intel.com> (raw) In-Reply-To: <20201214184917.GA17052@kadam> On Mon, Dec 14, 2020 at 09:49:17PM +0300, Dan Carpenter wrote: > On Sat, Dec 12, 2020 at 04:54:45PM +0800, Philip Li wrote: > > On Fri, Dec 11, 2020 at 04:42:00PM +0200, Ville Syrjälä wrote: > > > On Fri, Dec 11, 2020 at 01:24:49PM +0200, Tomi Valkeinen wrote: > > > > On 10/12/2020 20:06, kernel test robot wrote: > > > > > Hi Tomi, > > > > > > > > > > I love your patch! Perhaps something to improve: > > > > > > > > > > [auto build test WARNING on drm-intel/for-linux-next] > > > > > [also build test WARNING on linus/master v5.10-rc7] > > > > > [cannot apply to drm-tip/drm-tip anholt/for-next next-20201210] > > > > > [If your patch is applied to the wrong git tree, kindly drop us a note. > > > > > And when submitting patch, we suggest to use '--base' as documented in > > > > > https://git-scm.com/docs/git-format-patch ] > > > > > > > > > > url: https://github.com/0day-ci/linux/commits/Tomi-Valkeinen/drm-fix-and-cleanup-legacy-gamma-support/20201208-215917 > > > > > base: git://anongit.freedesktop.org/drm-intel for-linux-next > > > > > config: i386-randconfig-m021-20201209 (attached as .config) > > > > > compiler: gcc-9 (Debian 9.3.0-15) 9.3.0 > > > > > > > > > > If you fix the issue, kindly add following tag as appropriate > > > > > Reported-by: kernel test robot <lkp@intel.com> > > > > > > > > > > New smatch warnings: > > > > > drivers/gpu/drm/drm_color_mgmt.c:307 drm_crtc_legacy_gamma_set() error: potential null dereference 'blob'. (drm_property_create_blob returns null) > > > > > > > > I don't see how this could happen. There's no code path I see where drm_property_create_blob could > > > > return null... > > > > > > IIRC we've received multiple similar nonsense reports from lkp, but > > > no explanation why it thinks it could ever be null. Hmm, maybe there > > > is a codepath somewhere that has a null check on the return value? > > hi Dan, can you help on this to share some idea? > > > > The original report is at > > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/F3MVBRGF2R4URBNLNY3GMTSDZUCBX6RF/ > > Thanks, Philip. I've pushed a fix for this. Thanks Dan for this, we will pack the new code to run in the robot. > > It didn't show up if you had the cross function DB built, so it's not > something I would see in my testing. Got it, do you recommend this "cross function DB" is necessary for us to setup or not a must? Thanks > > regards, > dan carpenter > _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Philip Li <philip.li@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v2 2/2] drm: automatic legacy gamma support Date: Wed, 16 Dec 2020 09:06:50 +0800 [thread overview] Message-ID: <20201216010650.GA330@intel.com> (raw) In-Reply-To: <20201214184917.GA17052@kadam> [-- Attachment #1: Type: text/plain, Size: 2495 bytes --] On Mon, Dec 14, 2020 at 09:49:17PM +0300, Dan Carpenter wrote: > On Sat, Dec 12, 2020 at 04:54:45PM +0800, Philip Li wrote: > > On Fri, Dec 11, 2020 at 04:42:00PM +0200, Ville Syrjälä wrote: > > > On Fri, Dec 11, 2020 at 01:24:49PM +0200, Tomi Valkeinen wrote: > > > > On 10/12/2020 20:06, kernel test robot wrote: > > > > > Hi Tomi, > > > > > > > > > > I love your patch! Perhaps something to improve: > > > > > > > > > > [auto build test WARNING on drm-intel/for-linux-next] > > > > > [also build test WARNING on linus/master v5.10-rc7] > > > > > [cannot apply to drm-tip/drm-tip anholt/for-next next-20201210] > > > > > [If your patch is applied to the wrong git tree, kindly drop us a note. > > > > > And when submitting patch, we suggest to use '--base' as documented in > > > > > https://git-scm.com/docs/git-format-patch ] > > > > > > > > > > url: https://github.com/0day-ci/linux/commits/Tomi-Valkeinen/drm-fix-and-cleanup-legacy-gamma-support/20201208-215917 > > > > > base: git://anongit.freedesktop.org/drm-intel for-linux-next > > > > > config: i386-randconfig-m021-20201209 (attached as .config) > > > > > compiler: gcc-9 (Debian 9.3.0-15) 9.3.0 > > > > > > > > > > If you fix the issue, kindly add following tag as appropriate > > > > > Reported-by: kernel test robot <lkp@intel.com> > > > > > > > > > > New smatch warnings: > > > > > drivers/gpu/drm/drm_color_mgmt.c:307 drm_crtc_legacy_gamma_set() error: potential null dereference 'blob'. (drm_property_create_blob returns null) > > > > > > > > I don't see how this could happen. There's no code path I see where drm_property_create_blob could > > > > return null... > > > > > > IIRC we've received multiple similar nonsense reports from lkp, but > > > no explanation why it thinks it could ever be null. Hmm, maybe there > > > is a codepath somewhere that has a null check on the return value? > > hi Dan, can you help on this to share some idea? > > > > The original report is at > > https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org/thread/F3MVBRGF2R4URBNLNY3GMTSDZUCBX6RF/ > > Thanks, Philip. I've pushed a fix for this. Thanks Dan for this, we will pack the new code to run in the robot. > > It didn't show up if you had the cross function DB built, so it's not > something I would see in my testing. Got it, do you recommend this "cross function DB" is necessary for us to setup or not a must? Thanks > > regards, > dan carpenter >
next prev parent reply other threads:[~2020-12-16 1:10 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-08 13:57 [PATCH v2 0/2] drm: fix and cleanup legacy gamma support Tomi Valkeinen 2020-12-08 13:57 ` [PATCH v2 1/2] drm: add legacy support for using degamma for gamma Tomi Valkeinen 2020-12-08 15:55 ` Laurent Pinchart 2020-12-09 0:51 ` Daniel Vetter 2020-12-09 11:17 ` Tomi Valkeinen 2020-12-09 12:39 ` Daniel Vetter 2020-12-08 13:57 ` [PATCH v2 2/2] drm: automatic legacy gamma support Tomi Valkeinen 2020-12-08 15:59 ` Laurent Pinchart 2020-12-09 5:20 ` kernel test robot 2020-12-09 5:20 ` kernel test robot 2020-12-10 18:06 ` kernel test robot 2020-12-10 18:06 ` kernel test robot 2020-12-11 11:24 ` Tomi Valkeinen 2020-12-11 11:24 ` Tomi Valkeinen 2020-12-11 14:42 ` Ville Syrjälä 2020-12-11 14:42 ` Ville Syrjälä 2020-12-12 8:54 ` [kbuild-all] " Philip Li 2020-12-12 8:54 ` Philip Li 2020-12-14 18:49 ` [kbuild-all] " Dan Carpenter 2020-12-14 18:49 ` Dan Carpenter 2020-12-16 1:06 ` Philip Li [this message] 2020-12-16 1:06 ` Philip Li 2020-12-16 7:34 ` [kbuild-all] " Dan Carpenter 2020-12-16 7:34 ` Dan Carpenter
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201216010650.GA330@intel.com \ --to=philip.li@intel.com \ --cc=airlied@linux.ie \ --cc=dan.carpenter@oracle.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=hjc@rock-chips.com \ --cc=kbuild-all@lists.01.org \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux@armlinux.org.uk \ --cc=lkp@intel.com \ --cc=paul@crapouillou.net \ --cc=philippe.cornu@st.com \ --cc=tomi.valkeinen@ti.com \ --cc=yannick.fertre@st.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.