From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Michael Jamet <michael.jamet@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Yehezkel Bernat <yehezkel.bernat@intel.com>
Subject: Re: [PATCH 2/6] thunderbolt: property: Unify format_dwdata()/parse_dwdata()
Date: Wed, 3 Jun 2026 03:19:32 +0300 [thread overview]
Message-ID: <ah9zFHZsPCu05JSd@ashevche-desk.local> (raw)
In-Reply-To: <20260524-thunderbolt-big-endian-v1-2-6044edca78e7@weissschuh.net>
On Sun, May 24, 2026 at 03:06:44PM +0200, Thomas Weißschuh wrote:
> Both function do the same. They are about to change. To make that
> easier, implement one in terms of the other.
...
> static inline void format_dwdata(void *dst, const void *src, size_t dwords)
> {
> - cpu_to_be32_array(dst, src, dwords);
> + return parse_dwdata(dst, src, dwords);
Why return?
> }
Can't you simply kill this and use parse_dwdata everywhere?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-03 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 13:06 [PATCH 0/6] thunderbolt: property: Fix property parsing on big-endian Thomas Weißschuh
2026-05-24 13:06 ` [PATCH 1/6] thunderbolt: test: Make root_directory independent of host byte order Thomas Weißschuh
2026-05-24 13:06 ` [PATCH 2/6] thunderbolt: property: Unify format_dwdata()/parse_dwdata() Thomas Weißschuh
2026-06-03 0:19 ` Andy Shevchenko [this message]
2026-05-24 13:06 ` [PATCH 3/6] thunderbolt: property: Make format_dwdata() work on big-endian systems Thomas Weißschuh
2026-06-03 0:21 ` Andy Shevchenko
2026-05-24 13:06 ` [PATCH 4/6] thunderbolt: property: Convert byte order of numeric fields Thomas Weißschuh
2026-05-24 13:06 ` [PATCH 5/6] thunderbolt: property: Unify parse_dwdata()/format_dwdata() Thomas Weißschuh
2026-06-03 0:23 ` Andy Shevchenko
2026-05-24 13:06 ` [PATCH 6/6] thunderbolt: property: Make entry key modifications more visible Thomas Weißschuh
2026-06-03 0:25 ` Andy Shevchenko
2026-05-25 9:35 ` [PATCH 0/6] thunderbolt: property: Fix property parsing on big-endian Mika Westerberg
2026-05-25 10:32 ` Thomas Weißschuh
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=ah9zFHZsPCu05JSd@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@kernel.org \
--cc=yehezkel.bernat@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