From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: kuba@kernel.org, christophe.jaillet@wanadoo.fr,
fthain@telegraphics.com.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net/sonic: Fix some resource leaks in error handling paths
Date: Sat, 09 May 2020 16:32:17 -0700 (PDT) [thread overview]
Message-ID: <20200509.163217.1372289149714306397.davem@davemloft.net> (raw)
In-Reply-To: <fc5cf8da8e70ebb981a9fc3aec6834c74197f0ed.camel@perches.com>
From: Joe Perches <joe@perches.com>
Date: Sat, 09 May 2020 15:42:36 -0700
> David, maybe I missed some notification about Jakub's role.
>
> What is Jakub's role in relation to the networking tree?
He is the co-maintainer of the networking tree and you should respect
his actions and feedback as if it were coming from me.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: kuba@kernel.org, christophe.jaillet@wanadoo.fr,
fthain@telegraphics.com.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net/sonic: Fix some resource leaks in error handling paths
Date: Sat, 09 May 2020 23:32:17 +0000 [thread overview]
Message-ID: <20200509.163217.1372289149714306397.davem@davemloft.net> (raw)
In-Reply-To: <fc5cf8da8e70ebb981a9fc3aec6834c74197f0ed.camel@perches.com>
From: Joe Perches <joe@perches.com>
Date: Sat, 09 May 2020 15:42:36 -0700
> David, maybe I missed some notification about Jakub's role.
>
> What is Jakub's role in relation to the networking tree?
He is the co-maintainer of the networking tree and you should respect
his actions and feedback as if it were coming from me.
next prev parent reply other threads:[~2020-05-09 23:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 17:25 [PATCH] net/sonic: Fix some resource leaks in error handling paths Christophe JAILLET
2020-05-08 17:25 ` Christophe JAILLET
2020-05-08 23:28 ` Finn Thain
2020-05-08 23:28 ` Finn Thain
2020-05-09 0:57 ` Jakub Kicinski
2020-05-09 0:57 ` Jakub Kicinski
2020-05-09 1:57 ` Finn Thain
2020-05-09 1:57 ` Finn Thain
2020-05-09 2:04 ` Jakub Kicinski
2020-05-09 2:04 ` Jakub Kicinski
2020-05-09 1:54 ` Jakub Kicinski
2020-05-09 1:54 ` Jakub Kicinski
2020-05-09 16:47 ` Christophe JAILLET
2020-05-09 16:47 ` Christophe JAILLET
2020-05-09 18:13 ` Jakub Kicinski
2020-05-09 18:13 ` Jakub Kicinski
2020-05-09 20:31 ` Christophe JAILLET
2020-05-09 20:31 ` Christophe JAILLET
2020-05-09 22:42 ` Joe Perches
2020-05-09 22:42 ` Joe Perches
2020-05-09 23:32 ` David Miller [this message]
2020-05-09 23:32 ` David Miller
2020-05-09 23:41 ` Joe Perches
2020-05-09 23:41 ` Joe Perches
2020-05-09 23:52 ` Finn Thain
2020-05-09 23:52 ` Finn Thain
2020-05-09 6:15 Markus Elfring
2020-05-09 6:15 ` Markus Elfring
2020-05-09 23:45 ` Finn Thain
2020-05-09 23:45 ` Finn Thain
2020-05-10 5:30 ` Markus Elfring
2020-05-10 5:30 ` Markus Elfring
2020-05-10 8:25 ` Finn Thain
2020-05-10 8:25 ` Finn Thain
2020-05-10 9:07 ` Markus Elfring
2020-05-10 9:07 ` Markus Elfring
2020-05-11 0:28 ` Finn Thain
2020-05-11 0:28 ` Finn Thain
2020-05-11 6:48 ` Markus Elfring
2020-05-11 6:48 ` Markus Elfring
2020-05-12 0:08 ` Finn Thain
2020-05-12 0:08 ` Finn Thain
2020-05-12 6:38 ` Markus Elfring
2020-05-12 6:38 ` Markus Elfring
2020-05-13 1:14 ` Finn Thain
2020-05-13 1:14 ` Finn Thain
2020-05-13 5:07 ` net/sonic: Software evolution around the application of coding standards Markus Elfring
2020-05-13 5:07 ` Markus Elfring
2020-05-13 23:16 ` Finn Thain
2020-05-13 23:16 ` Finn Thain
2020-05-11 8:20 ` net/sonic: Fix some resource leaks in error handling paths Markus Elfring
2020-05-11 8:20 ` Markus Elfring
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=20200509.163217.1372289149714306397.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christophe.jaillet@wanadoo.fr \
--cc=fthain@telegraphics.com.au \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.