[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023121559-overfed-kisser-3923@gregkh>
Date: Fri, 15 Dec 2023 17:20:21 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Ayush Singh <ayushdevel1325@...il.com>
Cc: greybus-dev@...ts.linaro.org, johan@...nel.org, elder@...nel.org,
linux-kernel@...r.kernel.org, jkridner@...gleboard.org, nm@...com,
yujie.liu@...el.com
Subject: Re: [PATCH V2 1/1] greybus: gb-beagleplay: Remove use of pad bytes
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@...il.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
Powered by blists - more mailing lists