From: "Krzysztof Wilczyński" <kw@linux.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: "lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"mani@kernel.org" <mani@kernel.org>,
"marek.vasut+renesas@gmail.com" <marek.vasut+renesas@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v9 4/5] PCI: rcar-gen4: Add support for r8a779g0
Date: Wed, 3 Jul 2024 17:32:09 +0900 [thread overview]
Message-ID: <20240703083209.GB4117643@rocinante> (raw)
In-Reply-To: <TYCPR01MB1104021542E26342F961B1499D8DC2@TYCPR01MB11040.jpnprd01.prod.outlook.com>
[...]
> > After thinking about this a little more, I believe that it might be better
> > to follow what some other drivers have done, and simply add this guide as
> > a text file under a dedicated ../Documentation/admin-guide directory.
> >
> > We can then mention, or not, at the top of the file that there is a guide
> > available at this location for people to read on how to obtain and prepare
> > the firmware.
> >
> > Thoughts?
>
> Thank you for your comments. I agreed. So, may I send such a patch? Or, should
> I send whole patches as v10?
No need to send a new series. A small patch that I can pick would be fine.
Thank you!
Krzysztof
next prev parent reply other threads:[~2024-07-03 8:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 12:50 [PATCH v9 0/5] PCI: rcar-gen4: Add R-Car V4H support Yoshihiro Shimoda
2024-06-11 12:50 ` [PATCH v9 1/5] PCI: dwc: Add PCIE_PORT_{FORCE,LANE_SKEW} macros Yoshihiro Shimoda
2024-06-11 12:50 ` [PATCH v9 2/5] PCI: rcar-gen4: Add rcar_gen4_pcie_drvdata Yoshihiro Shimoda
2024-06-11 12:50 ` [PATCH v9 3/5] PCI: rcar-gen4: Add .ltssm_control() for other SoC support Yoshihiro Shimoda
2024-06-11 12:50 ` [PATCH v9 4/5] PCI: rcar-gen4: Add support for r8a779g0 Yoshihiro Shimoda
2024-06-18 7:09 ` Manivannan Sadhasivam
2024-06-18 8:10 ` Yoshihiro Shimoda
2024-06-19 8:52 ` Manivannan Sadhasivam
2024-06-23 13:16 ` Manivannan Sadhasivam
2024-06-29 19:56 ` Krzysztof Wilczyński
2024-07-01 4:07 ` Yoshihiro Shimoda
2024-07-01 20:43 ` Krzysztof Wilczyński
2024-07-02 12:22 ` Yoshihiro Shimoda
2024-07-03 8:32 ` Krzysztof Wilczyński [this message]
2024-07-03 9:34 ` Yoshihiro Shimoda
2024-07-02 17:14 ` Bjorn Helgaas
2024-07-02 23:57 ` Yoshihiro Shimoda
2024-06-11 12:50 ` [PATCH v9 5/5] misc: pci_endpoint_test: Document a policy about adding pci_device_id Yoshihiro Shimoda
2024-06-29 19:43 ` Krzysztof Wilczyński
2024-06-29 19:49 ` [PATCH v9 0/5] PCI: rcar-gen4: Add R-Car V4H support Krzysztof Wilczyński
2024-06-29 20:06 ` Krzysztof Wilczyński
2024-06-29 20:46 ` Bjorn Helgaas
2024-07-01 4:10 ` Yoshihiro Shimoda
2024-07-01 20:48 ` Krzysztof Wilczyński
2024-07-01 4:08 ` Yoshihiro Shimoda
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=20240703083209.GB4117643@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=robh@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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