From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linyu Yuan <quic_linyyuan@quicinc.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/3] usb: gadget: f_fs: remove ENTER() macro
Date: Sat, 25 Mar 2023 10:02:00 +0100 [thread overview]
Message-ID: <ZB64iI7O3un0VbUL@kroah.com> (raw)
In-Reply-To: <1679638227-20496-1-git-send-email-quic_linyyuan@quicinc.com>
On Fri, Mar 24, 2023 at 02:10:25PM +0800, Linyu Yuan wrote:
> ENTER() used to show function name which called during runtime, ftrace can
> be used to get same information, let's remove it.
>
> Signed-off-by: Linyu Yuan <quic_linyyuan@quicinc.com>
> ---
> v2: split to several changes according to v1 comments
> v1: https://lore.kernel.org/linux-usb/1679481369-30094-1-git-send-email-quic_linyyuan@quicinc.com/
>
> drivers/usb/gadget/function/f_fs.c | 94 --------------------------------------
> drivers/usb/gadget/function/u_fs.h | 2 -
> 2 files changed, 96 deletions(-)
As the kernel-test-bot points out, this patch does not build :(
next prev parent reply other threads:[~2023-03-25 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 6:10 [PATCH v2 1/3] usb: gadget: f_fs: remove ENTER() macro Linyu Yuan
2023-03-24 6:10 ` [PATCH v2 2/3] usb: gadget: f_fs: add more function with struct ffs_data *ffs parameter Linyu Yuan
2023-03-25 9:01 ` Greg Kroah-Hartman
2023-03-24 6:10 ` [PATCH v2 3/3] usb: gadget: f_fs: add dev name as prefix for pr_vdebug() Linyu Yuan
2023-03-25 9:00 ` Greg Kroah-Hartman
2023-03-26 2:55 ` Linyu Yuan
2023-03-26 6:29 ` Greg Kroah-Hartman
2023-03-27 1:54 ` Linyu Yuan
2023-03-27 5:46 ` Greg Kroah-Hartman
2023-03-24 16:03 ` [PATCH v2 1/3] usb: gadget: f_fs: remove ENTER() macro kernel test robot
2023-03-24 16:03 ` kernel test robot
2023-03-25 9:02 ` Greg Kroah-Hartman [this message]
2023-03-26 2:48 ` Linyu Yuan
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=ZB64iI7O3un0VbUL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_linyyuan@quicinc.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).