netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Wen Yang <wen.yang99@zte.com.cn>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@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: [1/3] net: xilinx: fix possible object reference leak
Date: Fri, 5 Apr 2019 11:18:41 +0200	[thread overview]
Message-ID: <b58d4aa3-198d-c75f-7a3e-319ce05c7f42@web.de> (raw)
In-Reply-To: <20190405081339.GO32590@kadam>

> We don't have a copy of the patch your discussing

I find this information inappropriate because I quoted
a questionable change.

Will any contributors get interested in another update for
the implementation of the function “axienet_probe”?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/net/ethernet/xilinx/xilinx_axienet_main.c?id=fa3a419d2f674b431d38748cb58fb7da17ee8949#n1576


> and it's not even clear who you're responding to.

I wonder about this feedback.

Regards,
Markus

      reply	other threads:[~2019-04-05  9:19 UTC|newest]

Thread overview: 10+ 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 ` [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-03-24  1:21 ` [PATCH 1/3] net: xilinx: " David Miller
2019-04-05  7:54 ` Markus Elfring
2019-04-05  8:13   ` Dan Carpenter
2019-04-05  9:18     ` Markus Elfring [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=b58d4aa3-198d-c75f-7a3e-319ce05c7f42@web.de \
    --to=markus.elfring@web.de \
    --cc=John.Linn@xilinx.com \
    --cc=anirudh@xilinx.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --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 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).