netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@caviumnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: hkallweit1@gmail.com, akpm@linux-foundation.org,
	sfr@canb.auug.org.au, netdev@vger.kernel.org
Subject: Re: Regression in 39461af74125 "bitmap: replace bitmap_{from,to}_u32array"
Date: Tue, 6 Feb 2018 19:26:23 +0300	[thread overview]
Message-ID: <20180206162623.haicwl6s7vjp62ht@yury-thinkpad> (raw)
In-Reply-To: <20180206.111736.1114727374069829674.davem@davemloft.net>

On Tue, Feb 06, 2018 at 11:17:36AM -0500, David Miller wrote:
> From: Heiner Kallweit <hkallweit1@gmail.com>
> Date: Mon, 5 Feb 2018 07:21:32 +0100
> 
> > Recently ethtool started to give incomplete values for supported and
> > advertised modes. There seems to be a regression in this commit:
> > The bit number parameter in the calls to bitmap_to_arr32() in
> > store_link_ksettings_for_user() should be __ETHTOOL_LINK_MODE_MASK_NBITS
> > instead of __ETHTOOL_LINK_MODE_MASK_NU32.
> > 
> > After having changed this ethtool behaves normally again.
> 
> I do not see the commit with the SHA1 ID from the Subject line in
> either Linus's nor my networking tree.
> 
> Where is that change?

It's in next-20180202.

Yury

  reply	other threads:[~2018-02-06 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  6:21 Regression in 39461af74125 "bitmap: replace bitmap_{from,to}_u32array" Heiner Kallweit
2018-02-05  7:17 ` Yury Norov
2018-02-06 16:17 ` David Miller
2018-02-06 16:26   ` Yury Norov [this message]
2018-02-06 16:42     ` David Miller
2018-02-06 17:03       ` Yury Norov
2018-02-06 17:53         ` 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=20180206162623.haicwl6s7vjp62ht@yury-thinkpad \
    --to=ynorov@caviumnetworks.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).