mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: chris.chenfeiyang@gmail.com, w@1wt.eu,
	"Paul E. McKenney" <paulmck@kernel.org>
Cc: "Feiyang Chen" <chenfeiyang@loongson.cn>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] nolibc: Add support for LoongArch
Date: Tue, 07 Feb 2023 15:25:50 +0100	[thread overview]
Message-ID: <1570009a-ca62-474d-b678-e6632b5b119e@app.fastmail.com> (raw)
In-Reply-To: <612947724da74327edb5e774de73d6d2a96d1648.1675734681.git.chenfeiyang@loongson.cn>

On Tue, Feb 7, 2023, at 03:09, chris.chenfeiyang@gmail.com wrote:
> From: Feiyang Chen <chenfeiyang@loongson.cn>
>
> Add support for LoongArch (32 and 64 bit) to nolibc.
>
> Signed-off-by: Feiyang Chen <chenfeiyang@loongson.cn>
> ---
> +
> +struct sys_stat_struct {
> +	unsigned long	st_dev;		/* Device.  */
> +	unsigned long	st_ino;		/* File serial number.  */
> +	unsigned int	st_mode;	/* File mode.  */
> +	unsigned int	st_nlink;	/* Link count.  */
> +	unsigned int	st_uid;		/* User ID of the file's owner.  */
> +	unsigned int	st_gid;		/* Group ID of the file's group. */
> +	unsigned long	st_rdev;	/* Device number, if device.  */
> +	unsigned long	__pad1;
> +	long		st_size;	/* Size of file, in bytes.  */
> +	int		st_blksize;	/* Optimal block size for I/O.  */
> +	int		__pad2;
> +	long		st_blocks;	/* Number 512-byte blocks allocated. */
> +	long		st_atime;	/* Time of last access.  */
> +	unsigned long	st_atime_nsec;
> +	long		st_mtime;	/* Time of last modification.  */
> +	unsigned long	st_mtime_nsec;
> +	long		st_ctime;	/* Time of last status change.  */
> +	unsigned long	st_ctime_nsec;
> +	unsigned int	__unused4;
> +	unsigned int	__unused5;
> +};

This definition should not be used after patch 1, I think you
should drop it.

      Arnd

  reply	other threads:[~2023-02-07 14:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  2:09 [PATCH 0/3] Add LoongArch support to nolibc chris.chenfeiyang
2023-02-07  2:09 ` [PATCH 1/3] nolibc: Add statx() support to implement sys_stat() chris.chenfeiyang
2023-02-07 14:30   ` Arnd Bergmann
2023-02-08  2:09     ` Feiyang Chen
2023-02-08  3:31       ` Willy Tarreau
2023-02-08  7:29         ` Arnd Bergmann
2023-02-08  7:42         ` Feiyang Chen
2023-02-08  8:06           ` Arnd Bergmann
2023-02-08  8:19             ` Willy Tarreau
2023-02-08  9:20               ` Feiyang Chen
     [not found]               ` <d0df35466db74097b8e70e28d35a4776@AcuMS.aculab.com>
2023-02-08 14:07                 ` Willy Tarreau
2023-02-08  8:07           ` Willy Tarreau
2023-02-07  2:09 ` [PATCH 2/3] nolibc: Add support for LoongArch chris.chenfeiyang
2023-02-07 14:25   ` Arnd Bergmann [this message]
2023-02-07  2:09 ` [PATCH 3/3] selftests/nolibc: " chris.chenfeiyang
2023-02-08  3:54   ` Willy Tarreau
2023-02-08  4:34     ` Paul E. McKenney
2023-02-08  6:39       ` Feiyang Chen

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=1570009a-ca62-474d-b678-e6632b5b119e@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=chenfeiyang@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=chris.chenfeiyang@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=paulmck@kernel.org \
    --cc=w@1wt.eu \
    /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®