public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	shuah <shuah@kernel.org>
Subject: Re: [GIT PULL] nolibc changes for 6.6-rc1
Date: Wed, 16 Aug 2023 05:12:20 +0200	[thread overview]
Message-ID: <20230816031220.GA18057@1wt.eu> (raw)
In-Reply-To: <85a03aa3-3d6e-3b16-d113-7d7f5a84bfb4@linuxfoundation.org>

On Tue, Aug 15, 2023 at 03:06:39PM -0600, Shuah Khan wrote:
> Pull worked fine and my verify_fixes script failed on the following patches.
> 
> Commit: 6c931bf0c732 ("selftests/nolibc: avoid buffer underrun in space printing")
> 	Fixes tag: Fixes: 8a27526f49f9 ("selftests/nolibc: add EXPECT_PTREQ, EXPECT_PTRNE and EXPECT_PTRER")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: 40f12898b479 ("tools/nolibc/stdio: add setvbuf() to set buffering mode")
> 	Fixes tag: Fixes: ecb7fe2cd610 ("selftests: line buffer test program's stdout")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> 
> 
> Will you be able to add the right commit IDs and resend the pull, so there
> are no mistakes if I guess it wrong.

Will do, many thanks for the check!
Willy

  reply	other threads:[~2023-08-16  3:13 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
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 [this message]
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=20230816031220.GA18057@1wt.eu \
    --to=w@1wt.eu \
    --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=skhan@linuxfoundation.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