mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Morton" <akpm@linux-foundation.org>,
	"Arnd Bergmann" <arnd@kernel.org>
Cc: "Balbir Singh" <bsingharora@gmail.com>,
	"Yang Yang" <yang.yang29@zte.com.cn>,
	"Wang Yaxin" <wang.yaxin@zte.com.cn>,
	"xu xin" <xu.xin16@zte.com.cn>,
	"Kun Jiang" <jiang.kun2@zte.com.cn>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] delayacct: fix uapi timespec64 definition
Date: Mon, 02 Feb 2026 21:47:22 +0100	[thread overview]
Message-ID: <ae0593b5-ead8-4b9f-b4c5-331d81b564f3@app.fastmail.com> (raw)
In-Reply-To: <20260202123754.1bf674cd3b58ce0cb2cfa006@linux-foundation.org>

On Mon, Feb 2, 2026, at 21:37, Andrew Morton wrote:
>>  	/*v17: delay max timestamp record*/
>> -	struct timespec64 cpu_delay_max_ts;
>> -	struct timespec64 blkio_delay_max_ts;
>> -	struct timespec64 swapin_delay_max_ts;
>> -	struct timespec64 freepages_delay_max_ts;
>> -	struct timespec64 thrashing_delay_max_ts;
>> -	struct timespec64 compact_delay_max_ts;
>> -	struct timespec64 wpcopy_delay_max_ts;
>> -	struct timespec64 irq_delay_max_ts;
>> +	struct __kernel_timespec cpu_delay_max_ts;
>> +	struct __kernel_timespec blkio_delay_max_ts;
>> +	struct __kernel_timespec swapin_delay_max_ts;
>> +	struct __kernel_timespec freepages_delay_max_ts;
>> +	struct __kernel_timespec thrashing_delay_max_ts;
>> +	struct __kernel_timespec compact_delay_max_ts;
>> +	struct __kernel_timespec wpcopy_delay_max_ts;
>> +	struct __kernel_timespec irq_delay_max_ts;
>>  } __uapi_arch_align;
>
> There's no __uapi_arch_align here in any tree I looked at?

My mistake, that was a remnant of a work-in-progress
series that I used to detect unintended padding in uapi
structures.

Thanks for fixing up the patch and applying the correct
version.

      Arnd

  reply	other threads:[~2026-02-02 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02  9:59 Arnd Bergmann
2026-02-02 13:08 ` wang.yaxin
2026-02-02 20:37 ` Andrew Morton
2026-02-02 20:47   ` Arnd Bergmann [this message]
2026-02-13  8:44 ` Geert Uytterhoeven

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=ae0593b5-ead8-4b9f-b4c5-331d81b564f3@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@kernel.org \
    --cc=bsingharora@gmail.com \
    --cc=jiang.kun2@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wang.yaxin@zte.com.cn \
    --cc=xu.xin16@zte.com.cn \
    --cc=yang.yang29@zte.com.cn \
    /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®