All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	gregkh@linuxfoundation.org, arnd@arndb.de, lpieralisi@kernel.org,
	shuah@kernel.org, kishon@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, bhelgaas@google.com,
	linux-arm-msm@vger.kernel.org, robh@kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Migrate PCI Endpoint Subsystem tests to Kselftest
Date: Thu, 19 Dec 2024 15:31:21 +0100	[thread overview]
Message-ID: <Z2QuORW5kXSrc1AX@ryzen> (raw)
In-Reply-To: <20241219000112.GE1444967@rocinante>

On Thu, Dec 19, 2024 at 09:01:12AM +0900, Krzysztof Wilczyński wrote:
> Hello,
> 
> > This series carries forward the effort to add Kselftest for PCI Endpoint
> > Subsystem started by Aman Gupta [1] a while ago. I reworked the initial version
> > based on another patch that fixes the return values of IOCTLs in
> > pci_endpoint_test driver and did many cleanups. Since the resulting work
> > modified the initial version substantially, I took over the authorship.
> > 
> > This series also incorporates the review comment by Shuah Khan [2] to move the
> > existing tests from 'tools/pci' to 'tools/testing/kselftest/pci_endpoint' before
> > migrating to Kselftest framework. I made sure that the tests are executable in
> > each commit and updated documentation accordingly.
> > 
> > NOTE: Patch 1 is strictly not related to this series, but necessary to execute
> > Kselftests with Qualcomm Endpoint devices. So this can be merged separately.
> 
> Applied to selftests, thank you!
> 
> [01/04] PCI: qcom-ep: Mark BAR0/BAR2 as 64bit BARs and BAR1/BAR3 as RESERVED
>         https://git.kernel.org/pci/pci/c/71ae1c3a342c
> 
> [02/04] misc: pci_endpoint_test: Fix the return value of IOCTL
>         https://git.kernel.org/pci/pci/c/7908208a2f6a
> 
> [03/04] selftests: Move PCI Endpoint tests from tools/pci to Kselftests
>         https://git.kernel.org/pci/pci/c/5c892b60e4c6
> 
> [04/04] selftests: pci_endpoint: Migrate to Kselftest framework
>         https://git.kernel.org/pci/pci/c/62f966e676b5
> 
> 	Krzysztof

I'm a bit surprised that this series was picked up,
since as you could see earlier in this same thread:
https://lore.kernel.org/linux-pci/20241219000112.GE1444967@rocinante/T/#m7bb0e624a4bf88f5cc13dc3804972c4fa9a79bcd

Mani suggested that my patch (which conflicts with this),
should be picked up first.

Is there a reason for the sudden chance of plans?

Please advice on how to proceed.


Kind regards,
Niklas

  reply	other threads:[~2024-12-19 14:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  8:01 [PATCH v3 0/4] Migrate PCI Endpoint Subsystem tests to Kselftest Manivannan Sadhasivam
2024-12-11  8:01 ` [PATCH v3 1/4] PCI: qcom-ep: Mark BAR0/BAR2 as 64bit BARs and BAR1/BAR3 as RESERVED Manivannan Sadhasivam
2024-12-11  8:01 ` [PATCH v3 2/4] misc: pci_endpoint_test: Fix the return value of IOCTL Manivannan Sadhasivam
2024-12-11  8:37   ` Damien Le Moal
2024-12-11  9:19     ` Manivannan Sadhasivam
2024-12-11  8:01 ` [PATCH v3 3/4] selftests: Move PCI Endpoint tests from tools/pci to Kselftests Manivannan Sadhasivam
2024-12-11  8:01 ` [PATCH v3 4/4] selftests: pci_endpoint: Migrate to Kselftest framework Manivannan Sadhasivam
2024-12-12  9:25 ` [PATCH v3 0/4] Migrate PCI Endpoint Subsystem tests to Kselftest Niklas Cassel
2024-12-16  6:03   ` Manivannan Sadhasivam
2024-12-18  9:19     ` Niklas Cassel
2024-12-19  0:01 ` Krzysztof Wilczyński
2024-12-19 14:31   ` Niklas Cassel [this message]
2024-12-19 15:55     ` Krzysztof Wilczyński
2024-12-19 20:17       ` Niklas Cassel

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=Z2QuORW5kXSrc1AX@ryzen \
    --to=cassel@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.