public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu, git@xilinx.com,
	bharat.kumar.gogada@xilinx.com, Hyun Kwon <hyun.kwon@xilinx.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Ravi Kiran Gummaluri <rgummal@xilinx.com>,
	Rob Herring <robh@kernel.org>, Sasha Levin <sashal@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI: xilinx-nwl: Enable the clock through CCF
Date: Wed, 23 Jun 2021 16:19:20 +0200	[thread overview]
Message-ID: <20210623141920.GB54420@rocinante> (raw)
In-Reply-To: <f15a9fca-0fb0-5f7a-e1c7-6c52df617a2e@xilinx.com>

Hi Michal,

[...]
> > Does it make sense for this change to be back-ported to stable and
> > long-term kernels?
> > 
> > I am asking to make sure we do the right thing here, as I can imagine
> > that older kernels (primarily because some folks could use, for example,
> > Ubuntu LTS releases for development) might often be used by people who
> > work with the Xilinx FPGAs and such.
> 
> I think that make sense to do so. I haven't had a time to take look at
> it closely but I think on Xilinx ZynqMP zcu102 board this missing patch
> is causing hang when standard debian 5.10 is used.

OK.  This definitely would be a good candidate for back-port then - it
might help quite a few folks to get their device going without this
troublesome hang you mentioned.

There are a few options as per:
  https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

You can send v3 adding the appropriate tag (see above link or the
comment below) or once this series (or mainly this patch) reaches Linus'
tree, then send a message to the stable maintainers mailing list to let
them know what any why to back-port.

At this point, I believe that adding the "Cc:" tag which includes the
"stable@vger.kernel.org" might be the best option as it would involve
the least amount of work to for Sasha et al.

What do you think?  Which option would you like to go for?

	Krzysztof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-23 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 13:23 [PATCH v2 0/2] PCI: xilinx-nwl: Add clock handling Michal Simek
2021-06-23 13:23 ` [PATCH v2 1/2] dt-bindings: pci: xilinx-nwl: Document optional clock property Michal Simek
2021-06-23 13:23 ` [PATCH v2 2/2] PCI: xilinx-nwl: Enable the clock through CCF Michal Simek
2021-06-23 13:53   ` Krzysztof Wilczyński
2021-06-23 14:00     ` Michal Simek
2021-06-23 14:19       ` Krzysztof Wilczyński [this message]
2021-06-25 10:48         ` Michal Simek

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=20210623141920.GB54420@rocinante \
    --to=kw@linux.com \
    --cc=bharat.kumar.gogada@xilinx.com \
    --cc=bhelgaas@google.com \
    --cc=git@xilinx.com \
    --cc=hyun.kwon@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=maz@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=rgummal@xilinx.com \
    --cc=robh@kernel.org \
    --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