From: Lee Jones <lee.jones@linaro.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "David E. Box" <david.e.box@linux.intel.com>,
Bjorn Helgaas <helgaas@kernel.org>,
dvhart@infradead.org, andy@infradead.org, bhelgaas@google.com,
alexey.budankov@linux.intel.com,
Andy Shevchenko <andy.shevchenko@gmail.com>,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH V8 1/5] PCI: Add defines for Designated Vendor-Specific Extended Capability
Date: Thu, 8 Oct 2020 08:29:12 +0100 [thread overview]
Message-ID: <20201008072912.GE1763265@dell> (raw)
In-Reply-To: <e09f4c44-e3d0-e14b-297f-6981516ea3bf@redhat.com>
On Wed, 07 Oct 2020, Hans de Goede wrote:
> Hi,
>
> On 10/7/20 8:54 AM, Lee Jones wrote:
> > On Tue, 06 Oct 2020, David E. Box wrote:
> >
> > > On Tue, 2020-10-06 at 19:51 -0500, Bjorn Helgaas wrote:
> > > > On Tue, Oct 06, 2020 at 03:45:54PM -0700, David E. Box wrote:
> > > > > Hi Bjorn,
> > > > >
> > > > > This patch has been acked and unchanged for weeks. Is it possible
> > > > > to
> > > > > get this pulled into next? We have SIOV and CXL related work that
> > > > > is
> > > > > using these definitions. Thanks.
> > > >
> > > > I acked it because I expected you to merge it along with the rest of
> > > > the series.
> > > >
> > > > I guess I could merge this patch via the PCI tree if you really want,
> > > > but that ends up being a hassle because we have to worry about which
> > > > order things get merged to Linus' tree. Better if the whole series
> > > > is
> > > > merged via the same tree.
> > >
> > > Agreed. The hope is that this series is ready for the next merge window
> > > but no ack yet on V8. And if the series does not make it I'd like this
> > > patch to at least get in.
> >
> > If Bjorn is happy to take this patch so late in the release cycle then
> > please go ahead. The other patches are due for v5.11.
>
> I agree (that the other patches are for 5.11) talking about merging
> this series patch 2 is a mfd patch and patches 3-5 are drivers/platform/x86
> patches.
>
> Lee, FYI I'm taking over drivers/platform/x86 maintainership from Andy.
Congratulations, Hans.
> I suggest that we merge the entire series through a single tree
> (with acks or reviewed-by-s from the other maintainer)
> either through the mfd tree or through the drivers/platform/x86
> tree. Since most changes are in drivers/platform/x86 the latter
> probably makes more sense, but either way works for me.
> So how would you like to proceed with this series ?
I'm happy either way, but bear in mind that, due to the intrinsic
heterogeneous nature of MFD, I already have infrastructure to easily
apply (and send pull-requests for) cross-subsystem patch-sets.
If however, you decide that you'd really like to take the set, that's
also fine but I will require a pull-request from an immutable branch.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-10-08 7:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 1:31 [PATCH V8 0/5] Intel Platform Monitoring Technology David E. Box
2020-10-03 1:31 ` [PATCH V8 1/5] PCI: Add defines for Designated Vendor-Specific Extended Capability David E. Box
2020-10-06 22:45 ` David E. Box
2020-10-07 0:51 ` Bjorn Helgaas
2020-10-07 1:47 ` David E. Box
2020-10-07 6:54 ` Lee Jones
2020-10-07 21:36 ` Hans de Goede
2020-10-08 7:29 ` Lee Jones [this message]
2020-10-08 11:13 ` Hans de Goede
2020-10-03 1:31 ` [PATCH V8 2/5] mfd: Intel Platform Monitoring Technology support David E. Box
2020-10-07 6:57 ` Lee Jones
2020-10-07 16:10 ` David E. Box
2020-10-08 7:32 ` Lee Jones
2020-11-10 10:39 ` Geert Uytterhoeven
2020-11-10 18:06 ` David E. Box
2020-10-03 1:31 ` [PATCH V8 3/5] platform/x86: Intel PMT class driver David E. Box
2020-10-03 1:31 ` [PATCH V8 4/5] platform/x86: Intel PMT Telemetry capability driver David E. Box
2020-10-03 1:31 ` [PATCH V8 5/5] platform/x86: Intel PMT Crashlog " David E. Box
2020-10-27 11:28 ` [PATCH V8 0/5] Intel Platform Monitoring Technology Hans de Goede
2020-10-29 1:50 ` David E. Box
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=20201008072912.GE1763265@dell \
--to=lee.jones@linaro.org \
--cc=alexey.budankov@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).