All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [omap-audio:peter/linux-next-wip 70/82] sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it.
Date: Fri, 20 Mar 2020 10:16:20 +0800	[thread overview]
Message-ID: <202003201017.II8le8jJ%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

tree:   https://github.com/omap-audio/linux-audio peter/linux-next-wip
head:   6ac31c0a3cce3aa9f6e4551095fc0e64c7ae58c0
commit: 912e5fb4149f3374bcb878634622866a8f71205d [70/82] omap: mcasp: add omap-mcasp.* and add to Kconfig, Makefile

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


coccinelle warnings: (new ones prefixed by >>)

>> sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it.

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

             reply	other threads:[~2020-03-20  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  2:16 kbuild test robot [this message]
2020-03-20  2:16 ` [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings kbuild test robot

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=202003201017.II8le8jJ%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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: link
Be 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.