From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Ricardo Ribalda Delgado <ricardo@ribalda.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
linux-media@vger.kernel.org, hverkuil@xs4all.nl
Subject: Re: [PATCH] yavta: Format type errors for non x86 arches
Date: Sat, 14 Sep 2024 03:27:22 +0300 [thread overview]
Message-ID: <20240914002722.GA29370@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMrC3HsbgV23hAQ0T9_97XkhKwn07WOfinXSQ14wZT8SgTfd2g@mail.gmail.com>
On Tue, Apr 02, 2024 at 03:59:56PM +0200, Ricardo Ribalda wrote:
> Hi Laurent
>
> I can see that you updated yavta recently...
>
> Any chance that you can take a look at this?
Patch applied, sorry for the delay.
> On Fri, Oct 20, 2023 at 9:07 AM Ricardo Ribalda Delgado
> <ricardo@ribalda.com> wrote:
> >
> > @Laurent Pinchart
> >
> > Friendly Ping :)
> >
> > On Wed, Sep 20, 2023 at 10:06 PM Sakari Ailus <sakari.ailus@iki.fi> wrote:
> > >
> > > Hi Ricardo,
> > >
> > > Thanks for the update.
> > >
> > > On Wed, Sep 20, 2023 at 02:59:39PM +0200, Ricardo Ribalda wrote:
> > > > mipsel64el, ppc64el, ia64, ppc64, sparc64 and x32 have different lenghts
> > > > for long long ints, which result in some compilation errors.
> > > >
> > > > Lets add some castings and inttypes macros to help the compiler deal with
> > > > this.
> > > >
> > > > We have to use the castings, because kernel types (__u64 et al) does not
> > > > seem to be compatible with inttypes macros.
> > > >
> > > > Signed-off-by: Ricardo Ribalda <ricardo@ribalda.com>
> > >
> > > It'd be great to address this in the kernel. The kernel UAPI integer types
> > > have been around for a very long time so there could be issues in doing
> > > that, too.
> > >
> > > Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > >
> > > --
> > > Kind regards,
> > >
> > > Sakari Ailus
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-09-14 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 12:59 [PATCH] yavta: Format type errors for non x86 arches Ricardo Ribalda
2023-09-20 13:06 ` Sakari Ailus
2023-10-20 7:07 ` Ricardo Ribalda Delgado
2024-04-02 13:59 ` Ricardo Ribalda
2024-09-14 0:27 ` Laurent Pinchart [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-19 14:01 Ricardo Ribalda
2023-09-19 20:07 ` Sakari Ailus
2023-09-19 20:10 ` Ricardo Ribalda
2023-09-19 20:22 ` Sakari Ailus
2023-09-19 21:03 ` Laurent Pinchart
2023-09-20 12:19 ` Ricardo Ribalda
2023-09-20 12:39 ` Sakari Ailus
2023-09-20 12:58 ` Ricardo Ribalda
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=20240914002722.GA29370@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=ricardo@ribalda.com \
--cc=sakari.ailus@iki.fi \
/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