From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robherring2@gmail.com>, Andy Gross <agross@codeaurora.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Niklas Cassel <niklas.cassel@linaro.org>
Subject: linux-next: manual merge of the devicetree tree with the qcom tree
Date: Tue, 2 Oct 2018 13:31:44 +1000 [thread overview]
Message-ID: <20181002133144.4ea80f23@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
drivers/soc/qcom/apr.c
between commit:
4fadb26574cb ("soc: qcom: apr: Avoid string overflow")
from the qcom tree and commit:
b2efb5b04591 ("soc: Convert to using %pOFn instead of device_node.name")
from the devicetree tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc drivers/soc/qcom/apr.c
index 716762d59c1f,4bda793ba6ae..000000000000
--- a/drivers/soc/qcom/apr.c
+++ b/drivers/soc/qcom/apr.c
@@@ -219,9 -219,9 +219,9 @@@ static int apr_add_device(struct devic
adev->domain_id = id->domain_id;
adev->version = id->svc_version;
if (np)
- strscpy(adev->name, np->name, APR_NAME_SIZE);
+ snprintf(adev->name, APR_NAME_SIZE, "%pOFn", np);
else
- strncpy(adev->name, id->name, APR_NAME_SIZE);
+ strscpy(adev->name, id->name, APR_NAME_SIZE);
dev_set_name(&adev->dev, "aprsvc:%s:%x:%x", adev->name,
id->domain_id, id->svc_id);
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-10-02 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 3:31 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-05 3:44 linux-next: manual merge of the devicetree tree with the qcom tree Stephen Rothwell
2026-03-17 16:19 Mark Brown
2026-03-17 17:09 ` Geert Uytterhoeven
2026-03-19 13:46 Mark Brown
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=20181002133144.4ea80f23@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agross@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=robherring2@gmail.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