From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Antoine Tenart" <antoine.tenart@bootlin.com>,
linux-pci@vger.kernel.org,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Nadav Haklai" <nadavh@marvell.com>,
"Victor Gu" <xigu@marvell.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Zachary Zhang" <zhangzg@marvell.com>,
"Wilson Ding" <dingwei@marvell.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] PCI: aardvark: Size bridges before resources allocation
Date: Fri, 6 Jul 2018 13:42:45 +0200 [thread overview]
Message-ID: <20180706134245.3a554b27@windsurf> (raw)
In-Reply-To: <20180706110130.GA14439@red-moon>
Hello,
On Fri, 6 Jul 2018 12:01:30 +0100, Lorenzo Pieralisi wrote:
> > It is a serious bug, but it is not a regression. I.e whatever is fixed
> > by this patch never worked. So if you take a conservative view on
> > pushing patches to stable and only want to fix regressions, this one
> > doesn't qualify. However, if you take a more open approach and say you
> > want to fix obvious bugs/issues even in older stable kernels, then
> > indeed this patch qualifies.
> >
> > If you are within the kernel developers with this more open approach to
> > sending patches to stable, then you can add:
> >
> > Fixes: 8c39d710363c1 ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > Cc: <stable@vger.kernel.org>
> >
> > when applying the patch. Unless of course you want me to resend the
> > patch series with this added. Just let met know what you prefer.
>
> It is up to you, I think it qualifies for stable kernels so I would
> send it but it is your choice, please let me know.
It's OK for me to have it in stable kernels. The fix is pretty obvious,
so you can add the Fixes/Cc tags when applying. Unless of course you
want me to resend an updated version.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-07-06 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 9:16 [PATCH 0/2] PCI: aardvark: misc improvements Thomas Petazzoni
2018-06-29 9:16 ` [PATCH 1/2] PCI: aardvark: Size bridges before resources allocation Thomas Petazzoni
2018-07-05 14:15 ` Lorenzo Pieralisi
2018-07-05 14:19 ` Thomas Petazzoni
2018-07-06 11:01 ` Lorenzo Pieralisi
2018-07-06 11:42 ` Thomas Petazzoni [this message]
2018-07-06 12:21 ` Lorenzo Pieralisi
2018-06-29 9:16 ` [PATCH 2/2] PCI: aardvark: Convert to use pci_host_probe() Thomas Petazzoni
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=20180706134245.3a554b27@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=antoine.tenart@bootlin.com \
--cc=bhelgaas@google.com \
--cc=dingwei@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=nadavh@marvell.com \
--cc=xigu@marvell.com \
--cc=zhangzg@marvell.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;
as well as URLs for NNTP newsgroup(s).