linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Wesley.Sheng@microchip.com, kurt.schwemmer@microsemi.com,
	Kurt.Schwemmer@microchip.com
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] switchtec: add customer events and comments PAX specific GFMS event
Date: Thu, 13 Sep 2018 10:05:01 -0600	[thread overview]
Message-ID: <8ad178e5-5444-681a-1eae-5f9aa0c66bfa@deltatee.com> (raw)
In-Reply-To: <DM2PR11MB0105E2CA7030B336AC140B26951A0@DM2PR11MB0105.namprd11.prod.outlook.com>

On 13/09/18 01:34 AM, Wesley.Sheng@microchip.com wrote:
> From: Wesley Sheng <_Wesley.Sheng@microchip.com_
> <mailto:Wesley.Sheng@microchip.com>>

Similar to your previous patches, these are mangled by your email
client. It also would have also been better to send a small patch series
instead of these three individual patches.

  
> reserved for customers to implement up to 6 vendor-specific events, 24
> bytes per event
> comments on PAX specific GFMS event

Why do we need to merge this? You didn't present any code using these
new fields so this seems useless.

> Signed-off-by: Wesley Sheng <Wesley.Sheng@microchip.com>
> ---
> include/linux/switchtec.h | 19 ++++++++++++++++---
> 1 file changed, 16 insertions(+), 3 deletions(-)
>  
> diff --git a/include/linux/switchtec.h b/include/linux/switchtec.h
> index ec93e93..e3cb8b8 100644
> --- a/include/linux/switchtec.h
> +++ b/include/linux/switchtec.h
> @@ -59,6 +59,12 @@ enum mrpc_status {
>          SWITCHTEC_MRPC_STATUS_INTERRUPTED = 0x100,
> };
>  
> +struct event {
> +       u32 hdr;
> +       u32 data[5];
> +};

This doesn't follow the way the other events are doing things, and you
didn't convert all the other events, so it just looks inconsistent.


Logan

           reply	other threads:[~2018-09-13 17:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DM2PR11MB0105E2CA7030B336AC140B26951A0@DM2PR11MB0105.namprd11.prod.outlook.com>]

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=8ad178e5-5444-681a-1eae-5f9aa0c66bfa@deltatee.com \
    --to=logang@deltatee.com \
    --cc=Kurt.Schwemmer@microchip.com \
    --cc=Wesley.Sheng@microchip.com \
    --cc=kurt.schwemmer@microsemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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 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).