From: David Miller <davem@davemloft.net>
To: mugunthanvnm@ti.com
Cc: netdev@vger.kernel.org, linux-omap@vger.kernel.org,
george.cherian@ti.com
Subject: Re: [PATCH 1/1] drivers: net : cpsw: Use netdev_name while requesting irq
Date: Mon, 09 Dec 2013 19:57:06 -0500 (EST) [thread overview]
Message-ID: <20131209.195706.1978243618769759438.davem@davemloft.net> (raw)
In-Reply-To: <52A58D61.9060404@ti.com>
From: Mugunthan V N <mugunthanvnm@ti.com>
Date: Mon, 9 Dec 2013 14:59:05 +0530
> commit 50a5fb068
This commit doesn't appear in any tree.
And any change which makes a real "struct device" return NULL
for dev_name() is broken.
I'm not applying this patch, you have completely failed to
provide any information necessary to support and justify
your change.
next prev parent reply other threads:[~2013-12-10 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 6:58 [PATCH 1/1] drivers: net : cpsw: Use netdev_name while requesting irq Mugunthan V N
2013-12-06 20:46 ` David Miller
2013-12-09 9:29 ` Mugunthan V N
2013-12-10 0:57 ` David Miller [this message]
2013-12-10 8:32 ` Mugunthan V N
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=20131209.195706.1978243618769759438.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=george.cherian@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--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 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).