From: David Miller <davem@davemloft.net>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org, jiri@resnulli.us
Subject: Re: [PATCH net-next 2/2] rocker: use netdev_err after register_netdev
Date: Thu, 06 Aug 2015 21:48:23 -0700 (PDT) [thread overview]
Message-ID: <20150806.214823.1691899568866315487.davem@davemloft.net> (raw)
In-Reply-To: <1438666278-35614-2-git-send-email-sfeldma@gmail.com>
From: sfeldma@gmail.com
Date: Mon, 3 Aug 2015 22:31:18 -0700
> From: Scott Feldman <sfeldma@gmail.com>
>
> After successful register_netdev, we can use netdev_err rather the more
> generic dev_err.
>
> Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Applied.
next prev parent reply other threads:[~2015-08-07 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 5:31 [PATCH net-next 1/2] rocker: NULL port if port probe fails sfeldma
2015-08-04 5:31 ` [PATCH net-next 2/2] rocker: use netdev_err after register_netdev sfeldma
2015-08-07 4:48 ` David Miller [this message]
2015-08-07 4:48 ` [PATCH net-next 1/2] rocker: NULL port if port probe fails David Miller
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=20150806.214823.1691899568866315487.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.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 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).