From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: kbuild test robot <lkp@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kbuild-all@01.org, linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [balbi-usb:testing/next 2/13] drivers/usb/phy/phy-tahvo.c:434:4: error: 'struct device_driver' has no member named 'dev_groups'; did you mean 'groups'?
Date: Fri, 09 Aug 2019 08:27:52 +0300 [thread overview]
Message-ID: <875zn6gb6v.fsf@gmail.com> (raw)
In-Reply-To: <201908082335.aajJntgU%lkp@intel.com>
Hi,
kbuild test robot <lkp@intel.com> writes:
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/balbi/usb.git testing/next
> head: d06a2c3f683a591efce9d02b2b60ef346df5ae02
> commit: 2a714ea6d90d9d1b510ba424652a2e3dfd547267 [2/13] USB: phy: tahvo: convert platform driver to use dev_groups
> config: sh-allmodconfig (attached as .config)
> compiler: sh4-linux-gcc (GCC) 7.4.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 2a714ea6d90d9d1b510ba424652a2e3dfd547267
> # save the attached .config to linux build tree
> GCC_VERSION=7.4.0 make.cross ARCH=sh
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> drivers/usb/phy/phy-tahvo.c:434:4: error: 'struct device_driver' has no member named 'dev_groups'; did you mean 'groups'?
> .dev_groups = tahvo_groups,
> ^~~~~~~~~~
looks like these patches depend on something else that's not upstream
yet. I'll drop the patches from my queue. Greg,if you'd like to add my
ack:
Acked-by: Felipe Balbi <felipe.balbi@linux.intel.com>
cheers
--
balbi
next prev parent reply other threads:[~2019-08-09 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 15:09 [balbi-usb:testing/next 2/13] drivers/usb/phy/phy-tahvo.c:434:4: error: 'struct device_driver' has no member named 'dev_groups'; did you mean 'groups'? kbuild test robot
2019-08-09 5:27 ` Felipe Balbi [this message]
2019-08-09 5:58 ` Greg Kroah-Hartman
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=875zn6gb6v.fsf@gmail.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.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: 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).