All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: jgg@ziepe.ca, dledford@redhat.com
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/9] Clean ups, refactror, additions
Date: Mon, 6 Jan 2020 08:44:30 -0500	[thread overview]
Message-ID: <b0fd4d9c-af68-9d8c-29df-aa371344c006@intel.com> (raw)
In-Reply-To: <20200106133845.119356.20115.stgit@awfm-01.aw.intel.com>

On 1/6/2020 8:41 AM, Dennis Dalessandro wrote:
> These patches add some recactoring and code clean ups to make things more
> organized. There is a performance optimization and new counter/debugging stats
> added as well. The new "API" that is added is a driver internal API not an
> actual "API" that is exposed to the outside.
> 
> ---
> 
> Grzegorz Andrejczuk (3):
>        IB/hfi1: Move common receive IRQ code to function
>        IB/hfi1: Decouple IRQ name from type
>        IB/hfi1: Return void in packet receiving functions
> 
> Mike Marciniszyn (6):
>        IB/hfi1: Move chip specific functions to chip.c
>        IB/hfi1: Add fast and slow handlers for receive context
>        IB/hfi1: IB/hfi1: Add an API to handle special case drop
>        IB/hfi1: Create API for auto activate
>        IB/hfi1: Add software counter for ctxt0 seq drop
>        IB/hfi1: Add RcvShortLengthErrCnt to hfi1stats
> 
> 
>   drivers/infiniband/hw/hfi1/chip.c           |  171 ++++++++++++++++++++++-----
>   drivers/infiniband/hw/hfi1/chip.h           |    8 +
>   drivers/infiniband/hw/hfi1/chip_registers.h |    1
>   drivers/infiniband/hw/hfi1/driver.c         |  151 +++++++++---------------
>   drivers/infiniband/hw/hfi1/hfi.h            |   66 ++++++++++
>   drivers/infiniband/hw/hfi1/init.c           |   81 ++-----------
>   drivers/infiniband/hw/hfi1/msix.c           |  106 +++++++++--------
>   drivers/infiniband/hw/hfi1/msix.h           |    1
>   drivers/infiniband/hw/hfi1/trace_rx.h       |    6 -
>   9 files changed, 337 insertions(+), 254 deletions(-)
> 
> --
> -Denny
> 

Forgot to mention these apply on top of the: wip/jgg-for-next branch.

-Denny

  parent reply	other threads:[~2020-01-06 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 13:41 [PATCH for-next 0/9] Clean ups, refactror, additions Dennis Dalessandro
2020-01-06 13:41 ` [PATCH for-next 1/9] IB/hfi1: Move chip specific functions to chip.c Dennis Dalessandro
2020-01-06 13:41 ` [PATCH for-next 2/9] IB/hfi1: Add fast and slow handlers for receive context Dennis Dalessandro
2020-01-06 13:41 ` [PATCH for-next 3/9] IB/hfi1: Move common receive IRQ code to function Dennis Dalessandro
2020-01-06 13:42 ` [PATCH for-next 4/9] IB/hfi1: IB/hfi1: Add an API to handle special case drop Dennis Dalessandro
2020-01-06 13:42 ` [PATCH for-next 5/9] IB/hfi1: Create API for auto activate Dennis Dalessandro
2020-01-06 13:42 ` [PATCH for-next 6/9] IB/hfi1: Decouple IRQ name from type Dennis Dalessandro
2020-01-06 13:42 ` [PATCH for-next 7/9] IB/hfi1: Return void in packet receiving functions Dennis Dalessandro
2020-01-06 13:42 ` [PATCH for-next 8/9] IB/hfi1: Add software counter for ctxt0 seq drop Dennis Dalessandro
2020-01-06 13:42 ` [PATCH for-next 9/9] IB/hfi1: Add RcvShortLengthErrCnt to hfi1stats Dennis Dalessandro
2020-01-06 13:44 ` Dennis Dalessandro [this message]
2020-01-10 15:15 ` [PATCH for-next 0/9] Clean ups, refactror, additions Jason Gunthorpe

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=b0fd4d9c-af68-9d8c-29df-aa371344c006@intel.com \
    --to=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@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.