linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentin Rothberg <valentinrothberg@gmail.com>
To: gregkh@google.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: staging/greybus: undefined Kconfig symbols
Date: Wed, 21 Sep 2016 08:30:01 +0200	[thread overview]
Message-ID: <CAD3Xx4JUgT+wBJZP-ez_-D7c3K3T9xhE3daKJ4S0-x_xwqMVUA@mail.gmail.com> (raw)

Hi Greg,

checkkconfigsymbols.py found some undefined Kconfig symbols (see
below) in the Makefile and Kconfig file.  I could not find any patch
adding those symbols.  Are there patches queued somewhere else?

Best regards,
 Valentin

GREYBUS_AUDIO_MSM8994
Referencing files: drivers/staging/greybus/Makefile
Similar symbols: GREYBUS_AUDIO, GREYBUS_GPIO, GREYBUS_SDIO, GREYBUS_USB
Commits changing symbol:
- d4f56b47a8fa ("staging: greybus: Add drivers/staging/greybus to the build")

MEDIA
Referencing files: drivers/staging/greybus/Kconfig
Similar symbols: COMEDI, EDAC, EISA, HID_CMEDIA, LANMEDIA, MDIO,
MEDIA_CEC, MEDIA_TUNER, MEMDMA0, MEMDMA1
Commits changing symbol:
- d4f56b47a8fa ("staging: greybus: Add drivers/staging/greybus to the build")
- 847175e8e660 ("greybus: audio: Fetch jack_mask, button_mask from
module's topology data")
- 64a7e2cceb75 ("greybus: audio: Added jack support to audio module")

USB_HSIC_USB3613
Referencing files: drivers/staging/greybus/Makefile
Similar symbols: USB_FSL_USB2, USB_GSPCA_SPCA561, USB_GSPCA_STK1135,
USB_GSPCA_T613, USB_HCD_SSB, USB_HSIC_USB3503, USB_HSIC_USB4604,
USB_RENESAS_USB3, USB_SI4713, USB_SISUSBVGA
Commits changing symbol:
- d4f56b47a8fa ("staging: greybus: Add drivers/staging/greybus to the build")
- 7d0493d191ab ("greybus: only build arche platform driver if usb3613
is enabled")

             reply	other threads:[~2016-09-21  6:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21  6:30 Valentin Rothberg [this message]
2016-09-21  7:39 ` staging/greybus: undefined Kconfig symbols Greg KH
2016-09-21 10:25   ` Valentin Rothberg
2016-09-21 10:34     ` Greg KH

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=CAD3Xx4JUgT+wBJZP-ez_-D7c3K3T9xhE3daKJ4S0-x_xwqMVUA@mail.gmail.com \
    --to=valentinrothberg@gmail.com \
    --cc=gregkh@google.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).