Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Willy Tarreau <w@1wt.eu>
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>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [GIT PULL] nolibc changes for 6.6-rc1
Date: Tue, 15 Aug 2023 12:13:24 -0600	[thread overview]
Message-ID: <9950607c-cafe-c011-7d5f-76a8a971beb0@linuxfoundation.org> (raw)
In-Reply-To: <29590d7b-40fd-0426-75c6-36667e344f6c@linuxfoundation.org>

On 8/15/23 08:39, Shuah Khan wrote:
> On 8/15/23 08:35, Willy Tarreau wrote:
>> On Tue, Aug 15, 2023 at 08:25:51AM -0600, Shuah Khan wrote:
>>>> 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.
>>
>> No problem, thanks for getting back :-)
>>
>>> 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
>>
>> Ah sorry for the misunderstanding, that's the branch name, I'll set a
>> tag then.
>>
> 
> No worries. Could you also share the test you run? I will pull
> you request and run tests.
> 

Please send either another pull request or send the tag details.

Also please join IRC channel #kselftest on OFTC. It will be easier
to chat. Unless I am traveling you can find me there Nick: shuah

thanks,
-- Shuah




  reply	other threads:[~2023-08-15 18:14 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 [this message]
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=9950607c-cafe-c011-7d5f-76a8a971beb0@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