All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Rocco Yue <rocco.yue@mediatek.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	David Ahern <dsahern@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, Rocco.Yue@gmail.com,
	chao.song@mediatek.com, zhuoliang.zhang@mediatek.com
Subject: Re: [PATCH net-next] ipv6: don't generate link-local addr in random or privacy mode
Date: Mon, 15 Nov 2021 19:40:08 -0700	[thread overview]
Message-ID: <69706525-65b1-8372-8ef1-1ee12e7bbc26@gmail.com> (raw)
In-Reply-To: <20211116022145.31322-1-rocco.yue@mediatek.com>

On 11/15/21 7:21 PM, Rocco Yue wrote:
> 
> Due to I can see this patch from the link below, I'm not sure why this
> happened, could you kindly tell me what the merge window is, so I can
> avoid such problem next time.
>   https://lore.kernel.org/netdev/20211113084636.11685-1-rocco.yue@mediatek.com/t/
>   https://lore.kernel.org/lkml/20211113084636.11685-1-rocco.yue@mediatek.com/T/

check patch status here:
    https://patchwork.kernel.org/project/netdevbpf/list/

check net-next status here:
    http://vger.kernel.org/~davem/net-next.html



_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: David Ahern <dsahern@gmail.com>
To: Rocco Yue <rocco.yue@mediatek.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	David Ahern <dsahern@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, Rocco.Yue@gmail.com,
	chao.song@mediatek.com, zhuoliang.zhang@mediatek.com
Subject: Re: [PATCH net-next] ipv6: don't generate link-local addr in random or privacy mode
Date: Mon, 15 Nov 2021 19:40:08 -0700	[thread overview]
Message-ID: <69706525-65b1-8372-8ef1-1ee12e7bbc26@gmail.com> (raw)
In-Reply-To: <20211116022145.31322-1-rocco.yue@mediatek.com>

On 11/15/21 7:21 PM, Rocco Yue wrote:
> 
> Due to I can see this patch from the link below, I'm not sure why this
> happened, could you kindly tell me what the merge window is, so I can
> avoid such problem next time.
>   https://lore.kernel.org/netdev/20211113084636.11685-1-rocco.yue@mediatek.com/t/
>   https://lore.kernel.org/lkml/20211113084636.11685-1-rocco.yue@mediatek.com/T/

check patch status here:
    https://patchwork.kernel.org/project/netdevbpf/list/

check net-next status here:
    http://vger.kernel.org/~davem/net-next.html



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

WARNING: multiple messages have this Message-ID (diff)
From: David Ahern <dsahern@gmail.com>
To: Rocco Yue <rocco.yue@mediatek.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	David Ahern <dsahern@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, Rocco.Yue@gmail.com,
	chao.song@mediatek.com, zhuoliang.zhang@mediatek.com
Subject: Re: [PATCH net-next] ipv6: don't generate link-local addr in random or privacy mode
Date: Mon, 15 Nov 2021 19:40:08 -0700	[thread overview]
Message-ID: <69706525-65b1-8372-8ef1-1ee12e7bbc26@gmail.com> (raw)
In-Reply-To: <20211116022145.31322-1-rocco.yue@mediatek.com>

On 11/15/21 7:21 PM, Rocco Yue wrote:
> 
> Due to I can see this patch from the link below, I'm not sure why this
> happened, could you kindly tell me what the merge window is, so I can
> avoid such problem next time.
>   https://lore.kernel.org/netdev/20211113084636.11685-1-rocco.yue@mediatek.com/t/
>   https://lore.kernel.org/lkml/20211113084636.11685-1-rocco.yue@mediatek.com/T/

check patch status here:
    https://patchwork.kernel.org/project/netdevbpf/list/

check net-next status here:
    http://vger.kernel.org/~davem/net-next.html



  reply	other threads:[~2021-11-16  2:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  6:55 [PATCH net-next] ipv6: don't generate link-local addr in random or privacy mode Rocco Yue
2021-11-09  6:55 ` Rocco Yue
2021-11-09  6:55 ` Rocco Yue
2021-11-13  8:46 ` Rocco Yue
2021-11-13  8:46   ` Rocco Yue
2021-11-13  8:46   ` Rocco Yue
2021-11-13 16:34   ` David Ahern
2021-11-13 16:34     ` David Ahern
2021-11-13 16:34     ` David Ahern
2021-11-16  2:21     ` Rocco Yue
2021-11-16  2:21       ` Rocco Yue
2021-11-16  2:21       ` Rocco Yue
2021-11-16  2:40       ` David Ahern [this message]
2021-11-16  2:40         ` David Ahern
2021-11-16  2:40         ` David Ahern
2021-11-17  5:09 [PATCH net-next v2] " Lorenzo Colitti
2021-11-17  7:17 ` [PATCH net-next] " Rocco Yue
2021-11-17  7:17   ` Rocco Yue
2021-11-17  7:17   ` Rocco Yue
2021-11-17  8:36   ` Lorenzo Colitti
2021-11-17  8:36     ` Lorenzo Colitti
2021-11-17  8:36     ` Lorenzo Colitti
2021-11-17  9:50     ` Maciej Żenczykowski
2021-11-17  9:50       ` Maciej Żenczykowski
2021-11-17  9:50       ` Maciej Żenczykowski
2021-11-17  5:59 Rocco Yue
2021-11-17  5:59 ` Rocco Yue

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=69706525-65b1-8372-8ef1-1ee12e7bbc26@gmail.com \
    --to=dsahern@gmail.com \
    --cc=Rocco.Yue@gmail.com \
    --cc=chao.song@mediatek.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rocco.yue@mediatek.com \
    --cc=yoshfuji@linux-ipv6.org \
    --cc=zhuoliang.zhang@mediatek.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 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.