Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
Date:   Sat, 21 Oct 2023 10:59:21 +0200
From:   Jonathan Bergh <bergh.jonathan@gmail.com>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: Fix warnings due to introduction of new
 typedefs
Message-ID: <ZTOS6eaygOA6nRKD@HP-ENVY-Notebook>
References: <20231021081409.67570-1-bergh.jonathan@gmail.com>
 <2023102111-sneak-abreast-8061@gregkh>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2023102111-sneak-abreast-8061@gregkh>
Precedence: bulk

On Sat, Oct 21, 2023 at 10:32:29AM +0200, Greg KH wrote:

Hi

>  This looks like a new version of a previously submitted patch, but you
>  did not list below the --- line any changes from the previous version.

This patch is a *new* patch which replaced a previous *series* of patches
so it was considered a *new* standalone patch, rather than a new version 
of the original series. 
  
> - Your patch did many different things all at once, making it difficult
>   to review.  All Linux kernel patches need to only do one thing at a
>   time.  If you need to do multiple things (such as clean up all coding
>   style issues in a file/driver), do it in a sequence of patches, each
>   one doing only one thing.

This patch only addresses removal of typedefs from the declarations 
and fixes up the implmentations that relied on those typedefs. The previous
advice was to not make breaking changes across patches, so this patch 
represents code changes which are as atomic as possible in a single patch
without breaking the build. It does not mix formatting / other changes
with the code change.