[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023121616-depict-unloving-525b@gregkh>
Date: Sat, 16 Dec 2023 08:19:51 +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 Sat, Dec 16, 2023 at 05:39:30AM +0530, Ayush Singh wrote:
> 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@...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
>
> The base commit of my tree is `0f5f12ac05f36f117e793656c3f560625e927f1b`.
> The tag is `next-20231205`.
>
> I can rebase to a newer tag if you wish.
Please rebase on the char-misc-next branch otherwise I can not take it.
thanks,
greg k-h
Powered by blists - more mailing lists