From: Pairman Guo <pairmanxlr@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
pairmanxlr@gmail.com, shuah@kernel.org,
valentina.manea.m@gmail.com
Subject: Re: Re: [PATCH] USBIP: Use fallthrough pseudo-keyword
Date: Fri, 16 Feb 2024 15:55:23 +0800 [thread overview]
Message-ID: <20240216075711.6752-2-pairmanxlr@gmail.com> (raw)
In-Reply-To: <2024021516-chapter-willed-ccf3@gregkh>
On Thu, Feb 15, 2024 at 11:14:49 +0800, Greg KH wrote:
> This is not needed in a changelog text.
Thanks for telling. I'm new to lkml and still learning about the format.
> > tools/usb/usbip/src/usbip.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/usb/usbip/src/usbip.c b/tools/usb/usbip/src/usbip.c
> > index f7c7220d9..ddcafb5c7 100644
> > --- a/tools/usb/usbip/src/usbip.c
> > +++ b/tools/usb/usbip/src/usbip.c
> > @@ -165,7 +165,7 @@ int main(int argc, char *argv[])
> > case '?':
> > printf("usbip: invalid option\n");
> > /* Terminate after printing error */
> > - /* FALLTHRU */
> > + fallthrough;
>
> Did you compile this? This is userspace code, and as-such, I don't
> think it has this keyword, does it?
I'm sorry for my hurrying. I ran ``make tools/usb`` with no warning or error,
so I sent this patch. Now it turns out ``make tools/usb`` doesn't cover
tools/usb/usbip. I tried again with ``./autogen.sh && ./configure && make``
and it indeed failed. Since usbip.c doesn't have any reference to
include/linux/compiler.h, it cannot use ``fallthrough``. Thanks again for
pointing out this error.
Thanks,
Pairman
prev parent reply other threads:[~2024-02-16 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 9:26 [PATCH] USBIP: Use fallthrough pseudo-keyword Pairman Guo
2024-02-15 10:14 ` Greg KH
2024-02-16 7:55 ` Pairman Guo [this message]
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=20240216075711.6752-2-pairmanxlr@gmail.com \
--to=pairmanxlr@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=valentina.manea.m@gmail.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).