From: Dan Carpenter <dan.carpenter@oracle.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Wen Yang <wen.yang99@zte.com.cn>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Anirudha Sarangi <anirudh@xilinx.com>,
John Linn <John.Linn@xilinx.com>,
Michal Simek <michal.simek@xilinx.com>,
Yi Wang <wang.yi59@zte.com.cn>
Subject: Re: [PATCH 1/3] net: xilinx: fix possible object reference leak
Date: Fri, 5 Apr 2019 11:13:39 +0300 [thread overview]
Message-ID: <20190405081339.GO32590@kadam> (raw)
In-Reply-To: <d2f169a0-b982-82ca-b2f1-963b8a579504@web.de>
Hi Markus,
Please don't add kernel-janitors to the CC list in the middle of the
conversation. Netdev people can review their own code. We don't have a
copy of the patch your discussing and it's not even clear who you're
responding to.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Michal Simek <michal.simek@xilinx.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Anirudha Sarangi <anirudh@xilinx.com>,
John Linn <John.Linn@xilinx.com>,
Wen Yang <wen.yang99@zte.com.cn>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] net: xilinx: fix possible object reference leak
Date: Fri, 05 Apr 2019 08:13:39 +0000 [thread overview]
Message-ID: <20190405081339.GO32590@kadam> (raw)
In-Reply-To: <d2f169a0-b982-82ca-b2f1-963b8a579504@web.de>
Hi Markus,
Please don't add kernel-janitors to the CC list in the middle of the
conversation. Netdev people can review their own code. We don't have a
copy of the patch your discussing and it's not even clear who you're
responding to.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Michal Simek <michal.simek@xilinx.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Anirudha Sarangi <anirudh@xilinx.com>,
John Linn <John.Linn@xilinx.com>,
Wen Yang <wen.yang99@zte.com.cn>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] net: xilinx: fix possible object reference leak
Date: Fri, 5 Apr 2019 11:13:39 +0300 [thread overview]
Message-ID: <20190405081339.GO32590@kadam> (raw)
In-Reply-To: <d2f169a0-b982-82ca-b2f1-963b8a579504@web.de>
Hi Markus,
Please don't add kernel-janitors to the CC list in the middle of the
conversation. Netdev people can review their own code. We don't have a
copy of the patch your discussing and it's not even clear who you're
responding to.
regards,
dan carpenter
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-05 8:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 3:04 [PATCH 1/3] net: xilinx: fix possible object reference leak Wen Yang
2019-03-22 3:04 ` Wen Yang
2019-03-22 3:04 ` [PATCH 2/3] net: ibm: " Wen Yang
2019-03-24 1:21 ` David Miller
2019-03-22 3:04 ` [PATCH 3/3] net: ethernet: ti: " Wen Yang
2019-03-24 1:22 ` David Miller
2019-04-05 8:27 ` [PATCH 3/3] " Markus Elfring
2019-04-05 8:27 ` Markus Elfring
2019-03-24 1:21 ` [PATCH 1/3] net: xilinx: " David Miller
2019-03-24 1:21 ` David Miller
2019-04-05 7:54 ` Markus Elfring
2019-04-05 7:54 ` Markus Elfring
2019-04-05 7:54 ` Markus Elfring
2019-04-05 8:13 ` Dan Carpenter [this message]
2019-04-05 8:13 ` Dan Carpenter
2019-04-05 8:13 ` Dan Carpenter
2019-04-05 9:18 ` [1/3] " Markus Elfring
2019-04-05 9:18 ` 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=20190405081339.GO32590@kadam \
--to=dan.carpenter@oracle.com \
--cc=John.Linn@xilinx.com \
--cc=Markus.Elfring@web.de \
--cc=anirudh@xilinx.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
/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.