From: Bjorn Helgaas <helgaas@kernel.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: linux-sh@vger.kernel.org, glaubitz@physik.fu-berlin.de,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH v3 09/35] drivers/pci/controller: SH7751 PCI Host bridge driver.
Date: Mon, 16 Oct 2023 14:52:09 -0500 [thread overview]
Message-ID: <20231016195209.GA1221606@bhelgaas> (raw)
In-Reply-To: <20231016172742.GA1215127@bhelgaas>
On Mon, Oct 16, 2023 at 12:27:42PM -0500, Bjorn Helgaas wrote:
> "git am" complained about a couple whitespace errors elsewhere in this
> series:
>
> Applying: arch/sh/boot/compressed/head_32.S: passing FDT address to initialize function.
> .git/rebase-apply/patch:25: trailing whitespace.
> Applying: drivers/irqchip: SH7751 IRL external encoder with enable gate.
> .git/rebase-apply/patch:33: new blank line at EOF.
BTW, I mentioned all these things and more a month or so ago:
https://lore.kernel.org/r/20230918191602.GA201859@bhelgaas
https://lore.kernel.org/r/20230918193337.GA203483@bhelgaas
https://lore.kernel.org/r/20230918193036.GA203163@bhelgaas
I *thought* this seemed familiar ;)
Bjorn
> On Sat, Oct 14, 2023 at 11:53:44PM +0900, Yoshinori Sato wrote:
> > pci-sh7751.h move from "arch/sh/drivers/pci/pci-sh7751.h"
> > pci-sh7751.c convert from "arch/sh/drivers/pci/pci-sh7751.c"
>
> Note the subject line conventions in drivers/pci (use "git log
> --oneline" to see them): use something like this:
>
> PCI: sh7751: Add SH7751 PCI host bridge driver
>
> with no period at the end.
>
> arch/sh/drivers/pci/pci-sh7751.h and arch/sh/drivers/pci/pci-sh7751.c
> still exist after applying this series. Better to have a single patch
> that moves the content from arch/sh/drivers/pci/ to
> drivers/pci/controller/.
>
> Neither file looks like a simple move; there's a lot of reorganization
> going on at the same time. It's really difficult to review a patch
> like that because we can't compare the content from before and after.
>
> If you make a patch that does the cleanup/reorganization, and a
> separate patch that is just a simple move, and you use "git mv" for
> the move, git should notice that this is just a rename, and that diff
> will be tiny.
>
> One of the reorganization patches should be to incorporate the
> pci-sh7751.h content directly into pci-sh7751.c. Since it's only used
> in pci-sh7751.c, there's really no advantage to having it in a
> separate file.
>
> Bjorn
>
> > Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> > ---
> > drivers/pci/controller/Kconfig | 9 +
> > drivers/pci/controller/Makefile | 1 +
> > drivers/pci/controller/pci-sh7751.c | 285 ++++++++++++++++++++++++++++
> > drivers/pci/controller/pci-sh7751.h | 267 ++++++++++++++++++++++++++
> > 4 files changed, 562 insertions(+)
> > create mode 100644 drivers/pci/controller/pci-sh7751.c
> > create mode 100644 drivers/pci/controller/pci-sh7751.h
> >
> > diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
> > index c0c3f2824990..037ff44bd1e8 100644
> > --- a/drivers/pci/controller/Kconfig
> > +++ b/drivers/pci/controller/Kconfig
> > @@ -342,6 +342,15 @@ config PCIE_XILINX_CPM
> > Say 'Y' here if you want kernel support for the
> > Xilinx Versal CPM host bridge.
> >
> > +config PCI_SH7751
> > + bool "Renesas SH7751 PCI controller"
> > + depends on OF
> > + depends on CPU_SUBTYPE_SH7751 || CPU_SUBTYPE_SH7751R || COMPILE_TEST
> > + select PCI_HOST_COMMON
> > + help
> > + Say 'Y' here if you want kernel to support the Renesas SH7751 PCI
> > + Host Bridge driver.
>
> Move this so the menu entries stay sorted by vendor name.
>
> Bjorn
prev parent reply other threads:[~2023-10-16 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1697199949.git.ysato@users.sourceforge.jp>
2023-10-14 14:53 ` [RFC PATCH v3 09/35] drivers/pci/controller: SH7751 PCI Host bridge driver Yoshinori Sato
2023-10-16 17:27 ` Bjorn Helgaas
2023-10-16 19:52 ` Bjorn Helgaas [this message]
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=20231016195209.GA1221606@bhelgaas \
--to=helgaas@kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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