All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: qede: Add support for coalescing config read/update.
Date: Tue, 28 Jun 2016 09:05:17 +0000	[thread overview]
Message-ID: <57723DCD.5020904@bfs.de> (raw)
In-Reply-To: <20160627194210.GA30526@mwanda>



Am 28.06.2016 09:26, schrieb Yuval Mintz:
>>> drivers/net/ethernet/qlogic/qede/qede_ethtool.c
>>>    429  static int qede_get_coalesce(struct net_device *dev,
>>>    430                               struct ethtool_coalesce *coal)
>>>    431  {
>>>    432          struct qede_dev *edev = netdev_priv(dev);
>>>    433
>>>    434          memset(coal, 0, sizeof(struct ethtool_coalesce));
>>>    435          edev->ops->common->get_coalesce(edev->cdev,
>>>    436                                          (u16 *)&coal->rx_coalesce_usecs,
>>>    437                                          (u16 *)&coal->tx_coalesce_usecs);
>>>
>>> This won't work on big endian systems.  Fix it so the function takes a
>>> u32 or make ->rx_coalesce_usecs a u16.
>>>
>> given you do a memset before, what are the chances that coal-
>>> rx_coalesce_usecs != 0 ?
>> Is there a dynamic update in the background ?
> 
> It's a getter; The entire purpose of the `get_coalesce' function is to fill
> those fields with actual values.
> [Although I noticed that the memset is clearing the `cmd' field,
> which isn't an intended result]
> 

ok i understand, wrong direction :)
re,
 wh

      parent reply	other threads:[~2016-06-28  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 19:42 qede: Add support for coalescing config read/update Dan Carpenter
2016-06-28  4:41 ` Sudarsana Kalluru
2016-06-28  7:17 ` walter harms
2016-06-28  7:26 ` Yuval Mintz
2016-06-28  9:05 ` walter harms [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=57723DCD.5020904@bfs.de \
    --to=wharms@bfs.de \
    --cc=kernel-janitors@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 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.