From: "Thomas Weißschuh" <linux@weissschuh.net>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>, Zhangjin Wu <falcon@tinylab.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/nolibc: add tests for multi-object linkage
Date: Tue, 17 Oct 2023 00:03:41 +0200 [thread overview]
Message-ID: <edd7c9f6-32cb-4f5d-920d-7bd6bdb7eea0@t-8ch.de> (raw)
In-Reply-To: <246fe818-57a7-4cee-a11b-390df3eee101@paulmck-laptop>
On 2023-10-16 09:24:19-0700, Paul E. McKenney wrote:
> On Thu, Oct 12, 2023 at 01:18:18PM -0700, Paul E. McKenney wrote:
> > On Thu, Oct 12, 2023 at 09:34:53PM +0200, Thomas Weißschuh wrote:
> > > On 2023-10-12 12:06:33-0700, Paul E. McKenney wrote:
> > > > On Thu, Oct 12, 2023 at 08:39:14PM +0200, Thomas Weißschuh wrote:
> > > > > On 2023-10-12 11:25:02-0700, Paul E. McKenney wrote:
> > > > > > [..]
> > >
> > > > > > I have a signed tag urgent/nolibc.2023.10.12a in the -rcu tree, so
> > > > > > please check the lead-in text for sanity. (Everything after the digital
> > > > > > signature is automatically generated.)
> > > > >
> > > > > Looks good. But it's only a listing of the commit subjects, correct?
> > > >
> > > > Pretty close, just a few added words on the last one.
> > > >
> > > > So the question is whether there is some larger issue that Linus should
> > > > be made aware of. If these are just simple fixes for simple bugs,
> > > > we should be good, but yes, I do need to ask. ;-)
> > >
> > > These are simple fixes for simple bugs.
> > >
> > > Do you always have to ask specifically or can I just mention it in the
> > > pull request in the future?
> >
> > I would be extremely happy to simply copy text from the pull request
> > into the signed tags. ;-)
> >
> > We would just need to agree on the format. For example, in this case,
> > there will eventually be two signed tags, one for the urgent pull
> > request early next week and another for the pull request for the upcoming
> > merge window.
> >
> > Proposals for the format?
>
> Actually, proposals for the signed-tag text for the urgent commits?
> Left to myself, I would use the same text shown below that I proposed
> last week.
Looks good.
The tags for urgent PRs seem good with one item per patch.
I guess for normal PRs one item per series would be fine.
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> tag urgent/nolibc.2023.10.12a
> Tagger: Paul E. McKenney <paulmck@kernel.org>
> Date: Thu Oct 12 10:50:08 2023 -0700
>
> Urgent pull request for nolibc into v6.6
>
> This pull request contains the following fixes:
>
> o tools/nolibc: i386: Fix a stack misalign bug on _start
>
> o MAINTAINERS: nolibc: update tree location
>
> o tools/nolibc: mark start_c as weak to avoid linker errors
> [..]
next prev parent reply other threads:[~2023-10-16 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 23:13 Thomas Weißschuh
2023-10-12 7:06 ` Willy Tarreau
2023-10-12 7:23 ` Thomas Weißschuh
2023-10-12 10:41 ` Paul E. McKenney
2023-10-12 10:51 ` Thomas Weißschuh
2023-10-12 18:25 ` Paul E. McKenney
2023-10-12 18:39 ` Thomas Weißschuh
2023-10-12 19:06 ` Paul E. McKenney
2023-10-12 19:34 ` Thomas Weißschuh
2023-10-12 20:18 ` Paul E. McKenney
2023-10-16 16:24 ` Paul E. McKenney
2023-10-16 22:03 ` Thomas Weißschuh [this message]
2023-10-16 22:56 ` Paul E. McKenney
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=edd7c9f6-32cb-4f5d-920d-7bd6bdb7eea0@t-8ch.de \
--to=linux@weissschuh.net \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--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®