Received-SPF: pass (google.com: domain of linux-kernel+bounces-1855-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <e60f7697-1a1a-46a4-9def-b59cae9777a3@gmail.com>
Date: Sat, 16 Dec 2023 05:39:30 +0530
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH V2 1/1] greybus: gb-beagleplay: Remove use of pad bytes
Content-Language: en-US
To: Greg KH <gregkh@linuxfoundation.org>
Cc: greybus-dev@lists.linaro.org, johan@kernel.org, elder@kernel.org,
 linux-kernel@vger.kernel.org, jkridner@beagleboard.org, nm@ti.com,
 yujie.liu@intel.com
References: <20231211065420.213664-1-ayushdevel1325@gmail.com>
 <20231211065420.213664-2-ayushdevel1325@gmail.com>
 <2023121559-overfed-kisser-3923@gregkh>
From: Ayush Singh <ayushdevel1325@gmail.com>
In-Reply-To: <2023121559-overfed-kisser-3923@gregkh>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 12/15/23 21:50, Greg KH wrote:

> On Mon, Dec 11, 2023 at 12:24:18PM +0530, Ayush Singh wrote:
>> Make gb-beagleplay greybus spec compliant by moving cport information to
>> transport layer instead of using `header->pad` bytes.
>>
>> Greybus HDLC frame now has the following payload:
>> 1. le16 cport
>> 2. gb_operation_msg_hdr msg_header
>> 3. u8 *msg_payload
>>
>> Fixes: ec558bbfea67 ("greybus: Add BeaglePlay Linux Driver")
>> Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>
>> ---
>>   drivers/greybus/gb-beagleplay.c | 55 ++++++++++++++++++++++++---------
>>   1 file changed, 41 insertions(+), 14 deletions(-)
> This doesn't apply against my char-misc-next branch at all, what did you
> generate it against?
>
> thanks,
>
> greg k-h

The base commit of my tree is 
`0f5f12ac05f36f117e793656c3f560625e927f1b`. The tag is `next-20231205`.

I can rebase to a newer tag if you wish.

Ayush Singh