From: Alexey Dobriyan <adobriyan@gmail.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [RFC] include/linux/make_type.h: Helpers for making u16/u32/u64 values
Date: Fri, 16 Feb 2024 09:23:48 +0300 [thread overview]
Message-ID: <bfb4c75e-8031-4dde-b881-21bdb238b802@p183> (raw)
In-Reply-To: <53297b2e-b7ff-4b92-b937-116cadaf8b6d@intel.com>
On Wed, Feb 14, 2024 at 06:55:38PM +0100, Michal Wajdeczko wrote:
>
>
> On 14.02.2024 18:39, Alexey Dobriyan wrote:
> > On Wed, Feb 14, 2024 at 07:32:10PM +0200, Andy Shevchenko wrote:
> >> On Wed, Feb 14, 2024 at 08:20:55PM +0300, Alexey Dobriyan wrote:
>
> ...
>
> >
> > Thirdly, there were no users posted.
>
> for make_u64() there is already one at [1]
> [1]
> https://elixir.bootlin.com/linux/v6.8-rc4/source/drivers/gpu/drm/xe/xe_gt_pagefault.c#L555
OK, this one doesn't truncate too.
Honestly wordpath.h _sucks_ as a name.
I'd go with stdint.h, at least this name is known from userspace.
next prev parent reply other threads:[~2024-02-16 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 17:20 Alexey Dobriyan
2024-02-14 17:32 ` Andy Shevchenko
2024-02-14 17:39 ` Alexey Dobriyan
2024-02-14 17:42 ` Andy Shevchenko
2024-02-14 17:55 ` Michal Wajdeczko
2024-02-16 6:23 ` Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 15:54 Michal Wajdeczko
2024-02-14 16:04 ` Andy Shevchenko
2024-02-14 17:02 ` Michal Wajdeczko
2024-02-14 17:15 ` Andy Shevchenko
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=bfb4c75e-8031-4dde-b881-21bdb238b802@p183 \
--to=adobriyan@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@intel.com \
/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
all inboxes | Powered by JetHome®