From: Ajith P V <ajithpv.linux@gmail.com>
To: tung.quang.nguyen@est.tech, jmaloy@redhat.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] tipc: replace deprecated strcpy with strscpy in tipc_bearer_get_name()
Date: Fri, 14 Aug 2026 16:08:46 +0000 [thread overview]
Message-ID: <20260814160846.338273-1-ajithpv.linux@gmail.com> (raw)
In-Reply-To: <GV1P189MB1988CAF7D299010DB0C80031C6DA2@GV1P189MB1988.EURP189.PROD.OUTLOOK.COM>
> net tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
> net-next tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
Thank you. I tried the correct net-next tree. The same patch applied successfully here also as shown below.
<path of the linux tree>/net-next$ ls
arch certs CREDITS Documentation fs init ipc Kconfig lib MAINTAINERS mm README samples security tools virt
block COPYING crypto drivers include io_uring Kbuild kernel LICENSES Makefile net rust scripts sound usr
<path of the linux tree>/net-next$ git remote -v
origin https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git (fetch)
origin https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git (push)
<path of the linux tree>/net-next$ git am ../../patches/v3-0001-tipc-replace-deprecated-strcpy-with-strscpy-in-ti.patch
Applying: tipc: replace deprecated strcpy with strscpy in tipc_bearer_get_name()
<path of the linux tree>/net-next$ git branch
* main
<path of the linux tree>/net-next$
Am I missing something?
prev parent reply other threads:[~2026-08-14 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 10:22 [PATCH net-next v3] tipc: replace deprecated strcpy with strscpy in tipc_bearer_get_name() Ajith P V
2026-08-14 9:00 ` Tung Quang Nguyen
2026-08-14 12:55 ` Ajith P V
2026-08-14 13:03 ` Tung Quang Nguyen
2026-08-14 16:08 ` Ajith P V [this message]
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=20260814160846.338273-1-ajithpv.linux@gmail.com \
--to=ajithpv.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.quang.nguyen@est.tech \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.