From: Shuah Khan <skhan@linuxfoundation.org>
To: Bjorn Helgaas <helgaas@kernel.org>,
Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
<aman1.gupta@samsung.com>
Cc: 'Manivannan Sadhasivam' <manivannan.sadhasivam@linaro.org>,
shradha.t@samsung.com, pankaj.dubey@samsung.com, kishon@ti.com,
lpieralisi@kernel.org, kw@linux.com, shuah@kernel.org,
linux-pci@vger.kernel.org, linux-kselftest@vger.kernel.org,
'Padmanabhan Rajanbabu' <p.rajanbabu@samsung.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: pci: pci-selftest: add support for PCI endpoint driver test
Date: Thu, 26 Jan 2023 13:57:21 -0700 [thread overview]
Message-ID: <7b3cbbd1-8c27-adf9-d2ed-c037f67bd697@linuxfoundation.org> (raw)
In-Reply-To: <20230117195903.GA142672@bhelgaas>
On 1/17/23 12:59, Bjorn Helgaas wrote:
> On Tue, Dec 27, 2022 at 10:45:26AM +0530, Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics wrote:
>> ...
>> Thanks for review and suggestion. I understand that we would like to
>> reuse and preserve the history of tools/pci/pcietest.c. So we have
>> two approaches:
>>
>> 1: Using git mv command move existing code from tools/pci/ to
>> tools/testing/selftest/drivers/pci/ and then update the file to
>> convert to kselftest framework. I thought about this but after
>> movement, when we move it to kselftest format it is going to be huge
>> churn and we will be having modification in almost all lines.
>>
>> 2: Develop kselftest based driver in
>> tools/testing/selftest/drivers/pci/ and eventually delete existing
>> file from tools/pci/ folder providing justification in commit
>> message.
>>
>> From my viewpoint, going with the second approach makes more sense
>> because if almost complete file is getting modified, and it will
>> make the review process complex and anyways there is not much code
>> reusability.
>>
>> Please let me know if you have any other thought
>> process or if I am missing anything to understand your approach.
>
> I vote for the first approach, with "git mv" and subsequent conversion
> (in separate patches, of course). If git knows about the move,
> "git log --follow" will be useful even though the conversion will be a
> big patch. Adding a new test with the connection to the old one only
> in the commit log makes more work for people who dig through the
> history in the future.
>
Thanks Bjorn for explaining this in more detail that I did.
Please send revised patches following the first approach.
thanks,
-- Shuah
next prev parent reply other threads:[~2023-01-26 20:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221007053726epcas5p357c35abb79327fee6327bc6493e0178c@epcas5p3.samsung.com>
2022-10-07 5:39 ` [PATCH] selftests: pci: pci-selftest: add support for PCI endpoint driver test Aman Gupta
2022-10-11 10:58 ` Kishon Vijay Abraham I
2022-10-21 6:56 ` Aman Gupta
2022-10-21 8:00 ` 'Manivannan Sadhasivam'
2022-11-01 14:02 ` Manivannan Sadhasivam
2022-11-01 17:19 ` Manivannan Sadhasivam
2022-12-21 8:30 ` Shunsuke Mie
2022-12-23 13:39 ` Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
2022-12-22 16:58 ` Shuah Khan
2022-12-22 17:45 ` Manivannan Sadhasivam
2022-12-22 17:49 ` Shuah Khan
2022-12-23 15:02 ` Manivannan Sadhasivam
2022-12-23 16:31 ` Shuah Khan
2022-12-27 5:15 ` Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
2023-01-17 19:59 ` Bjorn Helgaas
2023-01-26 20:57 ` Shuah Khan [this message]
2023-02-14 6:16 ` 'Manivannan Sadhasivam'
2023-03-08 11:06 ` Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
2023-01-17 8:12 ` Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
[not found] <CGME20221219043044epcas5p3d5476a9a5d6ae7a5cd2bb3fa92708e73@epcas5p3.samsung.com>
2022-12-19 4:30 ` Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
2022-12-21 7:24 ` 'Manivannan Sadhasivam'
2022-12-23 13:45 ` Aman Gupta/FDS SW /SSIR/Engineer/Samsung Electronics
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=7b3cbbd1-8c27-adf9-d2ed-c037f67bd697@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=aman1.gupta@samsung.com \
--cc=helgaas@kernel.org \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=p.rajanbabu@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=shradha.t@samsung.com \
--cc=shuah@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).