From: Felipe Balbi <balbi@kernel.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Cernekee <cernekee@gmail.com>,
linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
linux-usb@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] usb: gadget: bcm63xx_udc: fix up the error of undeclared usb_debug_root
Date: Thu, 24 Sep 2020 10:50:05 +0300 [thread overview]
Message-ID: <871rirehqq.fsf@kernel.org> (raw)
In-Reply-To: <1600061930-778-1-git-send-email-chunfeng.yun@mediatek.com>
[-- Attachment #1.1: Type: text/plain, Size: 469 bytes --]
Chunfeng Yun <chunfeng.yun@mediatek.com> writes:
> Fix up the build error caused by undeclared usb_debug_root
>
> Cc: stable <stable@vger.kernel.org>
> Fixes: a66ada4f241c("usb: gadget: bcm63xx_udc: create debugfs directory under usb root")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
$ patch -p1 --dry-run p.patch
/usr/bin/patch: **** Only garbage was found in the patch input.
--
balbi
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-24 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 5:38 [PATCH] usb: gadget: bcm63xx_udc: fix up the error of undeclared usb_debug_root Chunfeng Yun
2020-09-14 6:12 ` Greg Kroah-Hartman
2020-09-14 6:16 ` Chunfeng Yun
2020-09-24 7:50 ` Felipe Balbi [this message]
2020-09-24 8:28 ` Chunfeng Yun
2020-09-24 8:52 ` Felipe Balbi
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=871rirehqq.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cernekee@gmail.com \
--cc=chunfeng.yun@mediatek.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=stable@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).