From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: <kingdix10@qq.com>, <marek.vasut+renesas@gmail.com>,
<yoshihiro.shimoda.uh@renesas.com>, <lpieralisi@kernel.org>,
<kw@linux.com>, <manivannan.sadhasivam@linaro.org>,
<robh@kernel.org>, <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <linux-renesas-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: rcar-ep: Fix the issue of the name parameter when calling devm_request_mem_region
Date: Sat, 4 Jan 2025 11:37:47 +0300 [thread overview]
Message-ID: <5f8d43fe-25e3-450d-b5c2-2d69b9bc9923@omp.ru> (raw)
In-Reply-To: <tencent_59625EFD404130F5900D6FB48840AD428F05@qq.com>
On 1/4/25 6:39 AM, kingdix10@qq.com wrote:
> From: King Dix <kingdix10@qq.com>
>
> When using devm_request_mem_region to request a resource, if the passed
> variable is a stack string variable, it will lead to an oops issue when
> eecuting the command cat /proc/iomem.
>
> Fix this by replacing outbound_name with the name of the previously
> requested resource.
>
> Signed-off-by: King Dix <kingdix10@qq.com>
> ---
> drivers/pci/controller/pcie-rcar-ep.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/controller/pcie-rcar-ep.c b/drivers/pci/controller/pcie-rcar-ep.c
> index 047e2cef5afc..464f8f29390c 100644
> --- a/drivers/pci/controller/pcie-rcar-ep.c
> +++ b/drivers/pci/controller/pcie-rcar-ep.c
> @@ -107,7 +107,7 @@ static int rcar_pcie_parse_outbound_ranges(struct rcar_pcie_endpoint *ep,
> }
> if (!devm_request_mem_region(&pdev->dev, res->start,
> resource_size(res),
> - outbound_name)) {
> + res->name)) {
Why this strange indentation?
[...]
MBR, Sergey
next prev parent reply other threads:[~2025-01-04 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 3:39 [PATCH] PCI: rcar-ep: Fix the issue of the name parameter when calling devm_request_mem_region kingdix10
2025-01-04 8:37 ` Sergey Shtylyov [this message]
2025-01-05 5:57 ` [PATCH v2] " kingdix10
2025-01-05 16:53 ` Manivannan Sadhasivam
2025-01-07 0:59 ` kingdix10
2025-01-06 13:17 ` Lad, Prabhakar
2025-01-05 5:30 ` [PATCH] Original Patch Title kingdix10
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=5f8d43fe-25e3-450d-b5c2-2d69b9bc9923@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=bhelgaas@google.com \
--cc=kingdix10@qq.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marek.vasut+renesas@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox