Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Willy Tarreau <w@1wt.eu>, "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	shuah <shuah@kernel.org>
Subject: Re: [GIT PULL] nolibc changes for 6.6-rc1
Date: Tue, 15 Aug 2023 08:25:51 -0600	[thread overview]
Message-ID: <3efa3710-4e8b-d187-a24d-ff85858e37fe@linuxfoundation.org> (raw)
In-Reply-To: <20230806172245.GA26239@1wt.eu>

On 8/6/23 11:22, Willy Tarreau wrote:
> Hi Shuah, hi Paul,
> 
> I'm sending you the list of planned nolibc changes for 6.6. A doc update
> may possibly follow a bit later to try to document the contribution
> process. We also noticed a slight increase in binary sizes that might
> be fixed soon but I wouldn't bet on this since it will require lot of
> testing again and I'd rather postpone this by default. In any case I
> have no intent to push any significant updates/fixes for 6.6 at this
> point.
> 
> I'm also pasting a summary of the changes in this pull request, feel
> free to use it for the merge commit message if you need.
> 
> For any question or if anything is not clear, do not hesitate to ask!
> 
> Thanks,
> Willy
> 
> ----- changes ------
> Nolibc:
>    - improved portability by removing build errors with -ENOSYS
>    - added syscall6() on MIPS to support pselect6() and mmap()
>    - added setvbuf(), rmdir(), pipe(), pipe2()
>    - add support for ppc/ppc64
>    - environ is no longer optional
>    - fixed frame pointer issues at -O0
>    - dropped sys_stat() in favor of sys_statx()
>    - centralized _start_c() to remove lots of asm code
>    - switched size_t to __SIZE_TYPE__
> 
> Selftests:
>    - improved status reporting (success/warning/failure counts, path to log file)
>    - various code cleanups (indent, unused variables, ...)
>    - more consistent test numbering
>    - enabled compiler warnings
>    - dropped unreliable chmod_net test
>    - improved reliability (create /dev/zero & /tmp, rely less on /proc)
>    - new tests (brk/sbrk/mmap/munmap)
>    - improved compatibility with musl
>    - new run-nolibc-test target to build and run natively
>    - new run-libc-test target to build and run against native libc
>    - made the cmdline parser more reliable against boolean arguments
>    - dropped dependency on memfd for vfprintf() test
>    - nolibc-test is no longer stripped
>    - added support for extending ARCH via XARCH
> 
> Other:
>    - add Thomas as co-maintainer
> -----------
> 
> The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
> 
>    Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
> 
> are available in the Git repository at:
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git/ 20230806-for-6.6-1
> 
> for you to fetch changes up to d98c1e27e46e47a3ae67e1d048f153598ba82611:
> 
>    tools/nolibc: stackprotector.h: make __stack_chk_init static (2023-08-06 18:44:47 +0200)
> 

Hi Willy,

I am sorry for the delay on this. I was traveling last week
and getting back to digging myself out of emails.

I am having trouble pulling this request though:

git request-pull https://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git/ 20230806-for-6.6-1

gives me the following error

fatal: Not a valid revision: git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git/

I don't see a tag at https://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git

thanks,
-- Shuah

  reply	other threads:[~2023-08-15 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 17:22 [GIT PULL] nolibc changes for 6.6-rc1 Willy Tarreau
2023-08-15 14:25 ` Shuah Khan [this message]
2023-08-15 14:35   ` Willy Tarreau
2023-08-15 14:39     ` Shuah Khan
2023-08-15 18:13       ` Shuah Khan
2023-08-15 18:48         ` Willy Tarreau
2023-08-15 21:06           ` Shuah Khan
2023-08-16  3:12             ` Willy Tarreau
2023-08-16  8:35             ` Willy Tarreau
2023-08-16 14:21               ` Shuah Khan

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=3efa3710-4e8b-d187-a24d-ff85858e37fe@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=paulmck@kernel.org \
    --cc=shuah@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