From: "Krzysztof Wilczyński" <kw@linux.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Manivannan Sadhasivam <mani@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.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 v4 0/6] PCI: controllers: tidy code up
Date: Sat, 6 Jan 2024 14:27:23 +0900 [thread overview]
Message-ID: <20240106052723.GC1227754@rocinante> (raw)
In-Reply-To: <TYBPR01MB534178CDECD712FE68F8A446D8662@TYBPR01MB5341.jpnprd01.prod.outlook.com>
Hello,
[...]
> > > Changes from v3:
> > > https://lore.kernel.org/linux-pci/20231215022955.3574063-1-yoshihiro.shimoda.uh@renesas.com/
> > > - Based on the latest pci.git / next branch. So, I modified the patch 1/6
> > > for pci-layerscape.c.
Shimoda-san, don't use next when working on patches. I might have told you
this once before, per the following. Something that is easy to forget.
https://lore.kernel.org/all/20230828160712.GA2127814@rocinante/
This is the HEAD branch you should be using:
https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/log/
You should seldom use our "next" or the upstream "linux-next" when working
on a series you want to send to us. That is, unless someone explicitly asks
you to do so or the changes you wish to submit to be applied are simple.
> > > - Add Reviewed-by tag in the patch 4/6.
> > > - Fix locations of read/write accessors by grouped for readability in
> > > the patch 4/6.
> >
> > The series has got all the Mani's acks. The last nitpick was fixed in
> > v4. No more comments at least from my side. What about merging it in
> > (before merge window v6.8 is opened)?
>
> Serge, thank you for your comment.
>
> Hi Krzysztof, Lorenzo, Bjorn, Mani,
Hi. Happy New Year 2024!
> Would you apply this patch series into pci.git / next branch?
We don't apply specific series like that. Bjorn will collect other
branches, and then eventually update our "next", which then will be
picked up and the upstream "linux-next" will eventually include it.
> I confirmed that the patch series could be applied on the latest pci.git / next branch
[...]
I appreciate that. However, I now need to resolve some conflicts to
apply this series. See my comment above. :)
Krzysztof
next prev parent reply other threads:[~2024-01-06 5:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 5:38 [PATCH v4 0/6] PCI: controllers: tidy code up Yoshihiro Shimoda
2023-12-20 5:38 ` [PATCH v4 1/6] PCI: dwc: Drop host prefix from struct dw_pcie_host_ops Yoshihiro Shimoda
2023-12-20 5:38 ` [PATCH v4 2/6] PCI: dwc: Rename to .init in struct dw_pcie_ep_ops Yoshihiro Shimoda
2023-12-20 5:38 ` [PATCH v4 3/6] PCI: dwc: Rename to .get_dbi_offset " Yoshihiro Shimoda
2023-12-20 5:38 ` [PATCH v4 4/6] PCI: dwc: Add dw_pcie_ep_{read,write}_dbi[2] helpers Yoshihiro Shimoda
2023-12-20 5:38 ` [PATCH v4 5/6] PCI: iproc: fix -Wvoid-pointer-to-enum-cast warning Yoshihiro Shimoda
2023-12-20 5:38 ` [PATCH v4 6/6] PCI: rcar-gen4: " Yoshihiro Shimoda
2023-12-20 15:20 ` [PATCH v4 0/6] PCI: controllers: tidy code up Serge Semin
2024-01-05 10:59 ` Yoshihiro Shimoda
2024-01-06 5:27 ` Krzysztof Wilczyński [this message]
2024-01-09 1:34 ` Yoshihiro Shimoda
2024-01-10 0:21 ` Bjorn Helgaas
2024-01-10 2:01 ` Yoshihiro Shimoda
2024-01-06 8:33 ` Krzysztof Wilczyński
2024-01-06 8:42 ` Krzysztof Wilczyński
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=20240106052723.GC1227754@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.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=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 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.