From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: "sashal@kernel.org" <sashal@kernel.org>,
"Busch, Keith" <keith.busch@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"helgaas@kernel.org" <helgaas@kernel.org>
Subject: Re: [PATCH] PCI/VMD: Fix config addressing with bus offsets
Date: Wed, 24 Jul 2019 17:47:01 +0000 [thread overview]
Message-ID: <b3bd987dc87dcf8e39be6a9614bb91e4f38813a2.camel@intel.com> (raw)
In-Reply-To: <20190724111103.GA26018@e121166-lin.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Wed, 2019-07-24 at 12:11 +0100, Lorenzo Pieralisi wrote:
> On Tue, Jul 23, 2019 at 03:12:51PM +0000, Derrick, Jonathan wrote:
>
> [...]
>
> > > > Besides the stable issue, can we get this into 5.3?
> > >
> > > Usually we send fixes at -rc for patches that were merged in the
> > > previous merge window; this fix is not one of those so I think
> > > we will send it for v5.4 unless it is very urgent.
> > >
> > > We should still update stable info in the log appropriately
> > > before queuing it.
> > >
> > > Thanks,
> > > Lorenzo
> >
> > Sure. Had assumed it would be queued for 5.3 as it was submitted in 5.2
> > I will resubmit during 5.4 merge window and deal with stables later.
>
> It should not be that complicated to add stable tags (possibly
> with commit dependencies on stable kernels where the patch
> does not apply and require additional patches to be pulled),
> there is plenty of time to sort this out.
>
> Apologies for not picking it up for v5.3 - I should have asked
> you to just update the stable tag so that we could merge it.
>
> Lorenzo
No problem. I have another fix I need to include so I will do that
during 5.4 merge window
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3278 bytes --]
next prev parent reply other threads:[~2019-07-24 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 21:15 [PATCH] PCI/VMD: Fix config addressing with bus offsets Jon Derrick
2019-06-21 14:28 ` Lorenzo Pieralisi
2019-06-24 18:12 ` Derrick, Jonathan
2019-07-22 16:02 ` Derrick, Jonathan
2019-07-23 9:32 ` Lorenzo Pieralisi
2019-07-23 15:12 ` Derrick, Jonathan
2019-07-24 11:11 ` Lorenzo Pieralisi
2019-07-24 17:47 ` Derrick, Jonathan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-07 20:00 Jon Derrick
[not found] ` <20190610151839.EC55620862@mail.kernel.org>
2019-06-10 15:34 ` Derrick, Jonathan
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=b3bd987dc87dcf8e39be6a9614bb91e4f38813a2.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sashal@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 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).