From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_eth: fix TXALCR1 offsets
Date: Mon, 08 Jan 2018 19:32:09 +0000 [thread overview]
Message-ID: <20180108.143209.1582638715239179133.davem@davemloft.net> (raw)
In-Reply-To: <20180106212652.818833413@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Sun, 07 Jan 2018 00:26:47 +0300
> The TXALCR1 offsets are incorrect in the register offset tables, most
> probably due to copy&paste error. Luckily, the driver never uses this
> register. :-)
>
> Fixes: 4a55530f38e4 ("net: sh_eth: modify the definitions of register")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Applied.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_eth: fix TXALCR1 offsets
Date: Mon, 08 Jan 2018 14:32:09 -0500 (EST) [thread overview]
Message-ID: <20180108.143209.1582638715239179133.davem@davemloft.net> (raw)
In-Reply-To: <20180106212652.818833413@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Sun, 07 Jan 2018 00:26:47 +0300
> The TXALCR1 offsets are incorrect in the register offset tables, most
> probably due to copy&paste error. Luckily, the driver never uses this
> register. :-)
>
> Fixes: 4a55530f38e4 ("net: sh_eth: modify the definitions of register")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Applied.
next prev parent reply other threads:[~2018-01-08 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 21:26 [PATCH] sh_eth: fix TXALCR1 offsets Sergei Shtylyov
2018-01-06 21:26 ` Sergei Shtylyov
2018-01-08 19:32 ` David Miller [this message]
2018-01-08 19:32 ` 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=20180108.143209.1582638715239179133.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 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.