Netdev List
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@netronome.com>
To: David Miller <davem@davemloft.net>,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
	Carl Heymann <carl.heymann@netronome.com>
Subject: Re: [PATCH net-next 0/2] nfp: fix rtsym and XDP register handling in debug dump
Date: Fri, 15 Dec 2017 15:18:29 +0100	[thread overview]
Message-ID: <20171215141828.3m7f66ziv4fn33c2@netronome.com> (raw)
In-Reply-To: <20171214095026.11665-1-simon.horman@netronome.com>

On Thu, Dec 14, 2017 at 10:50:24AM +0100, Simon Horman wrote:
> Hi,
> 
> this series resolves two problems in the recently added debug dump facility.
> 
> * Correctly handle reading absolute rtysms
> * Correctly handle special-case PB register reads
> 
> These fixes are for code only present in net-next.

Hi Dave,

It seems that I made a thinko in the title of the cover letter.  s/XDP/XPB/
These changes do not relate to XDP.

> Carl Heymann (2):
>   nfp: fix absolute rtsym handling in debug dump
>   nfp: fix XPB register reads in debug dump
> 
>  .../net/ethernet/netronome/nfp/nfp_net_debugdump.c | 57 +++++++++++++++-------
>  1 file changed, 39 insertions(+), 18 deletions(-)
> 
> -- 
> 2.11.0
> 

  parent reply	other threads:[~2017-12-15 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  9:50 [PATCH net-next 0/2] nfp: fix rtsym and XDP register handling in debug dump Simon Horman
2017-12-14  9:50 ` [PATCH net-next 1/2] nfp: fix absolute rtsym " Simon Horman
2017-12-14  9:50 ` [PATCH net-next 2/2] nfp: fix XPB register reads " Simon Horman
2017-12-15 14:18 ` Simon Horman [this message]
2017-12-15 17:49   ` [PATCH net-next 0/2] nfp: fix rtsym and XDP register handling " 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=20171215141828.3m7f66ziv4fn33c2@netronome.com \
    --to=simon.horman@netronome.com \
    --cc=carl.heymann@netronome.com \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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