LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ying Xue <ying.xue@windriver.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	"jon.maloy@ericsson.com" <jon.maloy@ericsson.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"niveditas98@gmail.com" <niveditas98@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"tipc-discussion@lists.sourceforge.net" 
	<tipc-discussion@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tipc: Avoid copying bytes beyond the supplied data
Date: Thu, 23 May 2019 18:20:45 +0800	[thread overview]
Message-ID: <11c81207-54dd-16d5-3f33-1ccf45a06dac@windriver.com> (raw)
In-Reply-To: <00ce1b1e52ac4b729d982c86127334aa@svr-chch-ex1.atlnz.lc>

On 5/23/19 4:46 AM, Chris Packham wrote:
> On most distros that is generated from include/uapi in the kernel source 
> and packaged as part of libc or a kernel-headers package. So once this 
> patch is accepted and makes it into the distros 
> /usr/include/linux/tipc_config.h will have this fix.

Thanks for the clarification. You are right, so it's unnecessary to make
any change.

      reply	other threads:[~2019-05-23 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  3:45 [PATCH v2] tipc: Avoid copying bytes beyond the supplied data Chris Packham
2019-05-22  7:47 ` Ying Xue
2019-05-22 20:46   ` Chris Packham
2019-05-23 10:20     ` Ying Xue [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=11c81207-54dd-16d5-3f33-1ccf45a06dac@windriver.com \
    --to=ying.xue@windriver.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=davem@davemloft.net \
    --cc=jon.maloy@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=niveditas98@gmail.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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).