public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: psykose <alice@ayaya.dev>
To: linux-bluetooth@vger.kernel.org
Cc: alice@ayaya.dev
Subject: [PATCH BlueZ 2/3] client/player: use long long for off_t print
Date: Thu, 11 May 2023 02:22:51 +0200	[thread overview]
Message-ID: <20230511002252.30868-2-alice@ayaya.dev> (raw)
In-Reply-To: <20230511002252.30868-1-alice@ayaya.dev>

%lld is guaranteed to be a 64-bit int, which we enforce via
-D_FILE_OFFSET_BITS=64.

Signed-off-by: psykose <alice@ayaya.dev>
---
 client/player.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/client/player.c b/client/player.c
index 7719076c8..856997319 100644
--- a/client/player.c
+++ b/client/player.c
@@ -3578,7 +3578,7 @@ static int transport_send_seq(struct transport *transport, int fd, uint32_t num)
 
 		offset = lseek(fd, 0, SEEK_CUR);
 
-		bt_shell_echo("[seq %d %d.%03ds] send: %zd/%zd bytes",
+		bt_shell_echo("[seq %d %d.%03ds] send: %lld/%lld bytes",
 				transport->seq, secs,
 				(nsecs + 500000) / 1000000,
 				offset, transport->stat.st_size);
-- 
2.40.1


  reply	other threads:[~2023-05-11  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  0:22 [PATCH BlueZ 1/3] build: set _FILE_OFFSET_BITS and _TIME_BITS to 64 universally psykose
2023-05-11  0:22 ` psykose [this message]
2023-05-15 19:17   ` [PATCH BlueZ 2/3] client/player: use long long for off_t print Luiz Augusto von Dentz
2023-05-11  0:22 ` [PATCH BlueZ 3/3] tools/parser: use long long for time_t print psykose
2023-05-11  1:42 ` [BlueZ,1/3] build: set _FILE_OFFSET_BITS and _TIME_BITS to 64 universally bluez.test.bot
2023-05-11  2:14   ` alice

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=20230511002252.30868-2-alice@ayaya.dev \
    --to=alice@ayaya.dev \
    --cc=linux-bluetooth@vger.kernel.org \
    /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