public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Karthikey Kadati <karthikey3608@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] staging: octeon: Remove port status typedefs
Date: Mon, 19 Jan 2026 07:50:34 +0100	[thread overview]
Message-ID: <2026011949-carded-escapable-a029@gregkh> (raw)
In-Reply-To: <20260118171348.54963-1-karthikey3608@gmail.com>

On Sun, Jan 18, 2026 at 10:43:48PM +0530, Karthikey Kadati wrote:
> Remove cvmx_pip_port_status_t and cvmx_pko_port_status_t typedefs and
> replace them with struct cvmx_pip_port_status and struct
> cvmx_pko_port_status to match Linux kernel coding style.
> 
> This also updates the MIPS architecture headers to name the structs so
> they can be referenced by the staging driver. The anonymous struct
> definitions in the headers caused compilation errors when referenced
> directly, so they are now named structs.
> 
> Signed-off-by: Karthikey Kadati <karthikey3608@gmail.com>
> ---
> Changes in v6:
> - Actually removed the 'typedef' keyword from cvmx-pip.h (Greg KH).
> - Moved changelog history below the --- line (Greg KH).
> - Removed misleading Reported-by tag.

As the kernel test bot shows, this wasn't tested, which is what I asked
for you to do the last time this was submitted :(

I suggest working on something else please.

thanks,

greg k-h

      parent reply	other threads:[~2026-01-19  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 17:13 [PATCH v6] staging: octeon: Remove port status typedefs Karthikey Kadati
2026-01-19  4:34 ` kernel test robot
2026-01-19  6:48 ` kernel test robot
2026-01-19  6:50 ` Greg KH [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=2026011949-carded-escapable-a029@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=karthikey3608@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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