From: Yue Haibing <yuehaibing@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <johan@kernel.org>, <elder@kernel.org>,
<greybus-dev@lists.linaro.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] greybus: svc: Remove unused declarations
Date: Tue, 22 Aug 2023 22:49:05 +0800 [thread overview]
Message-ID: <db71380f-c84a-5f11-5ec8-4e81a0a061f0@huawei.com> (raw)
In-Reply-To: <2023082220-washbowl-shed-6be9@gregkh>
On 2023/8/22 22:32, Greg KH wrote:
> On Fri, Aug 18, 2023 at 08:43:38PM +0800, Yue Haibing wrote:
>> Commit 84427943d2da ("greybus: svc: drop legacy-protocol dependency")
>> removed these implementations but not the declarations.
>>
>> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
>> ---
>> include/linux/greybus/svc.h | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/include/linux/greybus/svc.h b/include/linux/greybus/svc.h
>> index 5afaf5f06856..da547fb9071b 100644
>> --- a/include/linux/greybus/svc.h
>> +++ b/include/linux/greybus/svc.h
>> @@ -100,7 +100,4 @@ bool gb_svc_watchdog_enabled(struct gb_svc *svc);
>> int gb_svc_watchdog_enable(struct gb_svc *svc);
>> int gb_svc_watchdog_disable(struct gb_svc *svc);
>>
>> -int gb_svc_protocol_init(void);
>> -void gb_svc_protocol_exit(void);
>> -
>> #endif /* __SVC_H */
>> --
>> 2.34.1
>>
>
> Nice, how did you find these?
Just use grep to check like below, then filter out known false item
grep -rP --include=*.h '^(?:\w+\s+){1,3}\*{0,3}\s{0,3}\w+[\t]*\(' * |grep -P -oh '\w+\s*\('|sort| uniq -c| sort -n| grep -P '^\s+1\b'|sed -r -e 's/^\s+1\s+//' -e 's/\(//'|while read line ;
do
CNT=`git grep -w $line |wc -l` ;
if [ $CNT -eq 1 ];then
git grep -wn $line
fi
done
> .
>
next prev parent reply other threads:[~2023-08-22 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 12:43 Yue Haibing
2023-08-22 14:32 ` Greg KH
2023-08-22 14:49 ` Yue Haibing [this message]
2023-08-23 7:44 ` Johan Hovold
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=db71380f-c84a-5f11-5ec8-4e81a0a061f0@huawei.com \
--to=yuehaibing@huawei.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--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
all inboxes | Powered by JetHome®