From: David Miller <davem@davemloft.net>
To: ivan@de.ibm.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, chunkeey@gmail.com
Subject: Re: [PATCH v2] net/ibm/emac: wrong emac_calc_base call was used by typo
Date: Mon, 03 Sep 2018 21:51:07 -0700 (PDT) [thread overview]
Message-ID: <20180903.215107.929144059014660952.davem@davemloft.net> (raw)
In-Reply-To: <20180903072628.19986-1-ivan@de.ibm.com>
From: Ivan Mikhaylov <ivan@de.ibm.com>
Date: Mon, 3 Sep 2018 10:26:28 +0300
> __emac_calc_base_mr1 was used instead of __emac4_calc_base_mr1
> by copy-paste mistake for emac4syn.
>
> Fixes: 45d6e545505fd32edb812f085be7de45b6a5c0af ("net/ibm/emac: add 8192 rx/tx fifo size")
> Signed-off-by: Ivan Mikhaylov <ivan@de.ibm.com>
Applied.
prev parent reply other threads:[~2018-09-04 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 7:26 [PATCH v2] net/ibm/emac: wrong emac_calc_base call was used by typo Ivan Mikhaylov
2018-09-04 4:51 ` David Miller [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=20180903.215107.929144059014660952.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chunkeey@gmail.com \
--cc=ivan@de.ibm.com \
--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 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).