From: Ekansh Gupta <quic_ekangupt@quicinc.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <srinivas.kandagatla@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<quic_bkumar@quicinc.com>, <linux-kernel@vger.kernel.org>,
<quic_chennak@quicinc.com>, <dri-devel@lists.freedesktop.org>,
<arnd@arndb.de>
Subject: Re: [PATCH v1 2/4] misc: fastrpc: Rename fastrpc.c to fastrpc_main.c
Date: Thu, 21 Nov 2024 11:54:21 +0530 [thread overview]
Message-ID: <6e1fa7cc-c80b-40c1-aee5-d2e954ae1513@quicinc.com> (raw)
In-Reply-To: <2024111841-egotistic-unranked-ad4a@gregkh>
On 11/18/2024 7:28 PM, Greg KH wrote:
> On Mon, Nov 18, 2024 at 02:10:44PM +0530, Ekansh Gupta wrote:
>> Rename the main fastrpc source file to accomodate new files to be
>> compiled in the same kernel object.
>>
>> Signed-off-by: Ekansh Gupta <quic_ekangupt@quicinc.com>
>> ---
>> drivers/misc/fastrpc/Makefile | 1 +
>> drivers/misc/fastrpc/{fastrpc.c => fastrpc_main.c} | 0
>> 2 files changed, 1 insertion(+)
>> rename drivers/misc/fastrpc/{fastrpc.c => fastrpc_main.c} (100%)
>>
>> diff --git a/drivers/misc/fastrpc/Makefile b/drivers/misc/fastrpc/Makefile
>> index 77fd2b763b6b..020d30789a80 100644
>> --- a/drivers/misc/fastrpc/Makefile
>> +++ b/drivers/misc/fastrpc/Makefile
>> @@ -1,2 +1,3 @@
>> # SPDX-License-Identifier: GPL-2.0
>> obj-$(CONFIG_QCOM_FASTRPC) += fastrpc.o
>> +fastrpc-objs := fastrpc_main.o
>> \ No newline at end of file
>> diff --git a/drivers/misc/fastrpc/fastrpc.c b/drivers/misc/fastrpc/fastrpc_main.c
>> similarity index 100%
>> rename from drivers/misc/fastrpc/fastrpc.c
>> rename to drivers/misc/fastrpc/fastrpc_main.c
> Why not just "main.c"? You are in your own subdir, no need for the
> fastrpc_* prefix anymore, right?
Ack. I will update the names in next patchset. Thanks.
--ekansh
> thanks,
>
> greg "naming is hard" k-h
next prev parent reply other threads:[~2024-11-21 6:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 8:40 [PATCH v1 0/4] Add debugfs support for fastrpc driver Ekansh Gupta
2024-11-18 8:40 ` [PATCH v1 1/4] misc: fastrpc: Move fastrpc driver to misc/fastrpc/ Ekansh Gupta
2024-11-18 8:40 ` [PATCH v1 2/4] misc: fastrpc: Rename fastrpc.c to fastrpc_main.c Ekansh Gupta
2024-11-18 13:58 ` Greg KH
2024-11-21 6:24 ` Ekansh Gupta [this message]
2024-11-18 8:40 ` [PATCH v1 3/4] misc: fastrpc: Introduce fastrpc_shared.h header Ekansh Gupta
2024-11-18 13:58 ` Greg KH
2024-11-21 6:29 ` Ekansh Gupta
2024-11-18 8:40 ` [PATCH v1 4/4] misc: fastrpc: Add debugfs support for fastrpc Ekansh Gupta
2024-11-18 14:02 ` Greg KH
2024-11-21 6:42 ` Ekansh Gupta
2024-11-21 13:30 ` Greg KH
2024-11-21 18:53 ` Dmitry Baryshkov
2024-12-02 9:57 ` Ekansh Gupta
2024-12-02 12:48 ` Dmitry Baryshkov
2024-12-03 5:21 ` Ekansh Gupta
2024-12-03 11:57 ` Dmitry Baryshkov
2025-04-11 8:25 ` Ekansh Gupta
2025-04-14 7:11 ` Deepika Singh
2025-04-14 7:48 ` Dmitry Baryshkov
2025-04-14 7:56 ` Dmitry Baryshkov
2025-04-21 6:11 ` Deepika Singh
2025-04-21 8:14 ` Dmitry Baryshkov
2025-04-15 13:17 ` Greg KH
2025-04-21 8:21 ` Deepika Singh
2025-04-21 8:49 ` Greg KH
2025-04-14 7:44 ` Dmitry Baryshkov
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=6e1fa7cc-c80b-40c1-aee5-d2e954ae1513@quicinc.com \
--to=quic_ekangupt@quicinc.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bkumar@quicinc.com \
--cc=quic_chennak@quicinc.com \
--cc=srinivas.kandagatla@linaro.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