From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Jason Baron <jbaron@akamai.com>,
Jim Cromie <jim.cromie@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/3] dyndbg: add source file name to prefix
Date: Tue, 27 Jun 2023 17:01:15 +0200 [thread overview]
Message-ID: <2023062705-foil-playing-b2da@gregkh> (raw)
In-Reply-To: <79a77af6-c5f5-4abb-ae46-cdcf4d40b75e@t-8ch.de>
On Tue, Jun 27, 2023 at 04:57:35PM +0200, Thomas Weißschuh wrote:
> On 2023-06-27 16:47:26+0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 27, 2023 at 04:30:56PM +0200, Thomas Weißschuh wrote:
> > > Hi Luis and Greg,
> > >
> > > it seems you are the ones picking up patches for dyndbg.
> > >
> > > Could you take a look at this series?
> > > It has Acks from both Jason and Jim.
> >
> > It's the middle of the merge window, we can't take anything new, sorry.
>
> Just noticed this, too. Sorry for the noise.
>
> > Care to submit it after 6.5-rc1 is out?
>
> I'll ping again should it still apply cleanly to 6.5-rc1
> othewise I'll resend.
Resend would be good as this is long gone from out inboxes...
prev parent reply other threads:[~2023-06-27 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 2:01 [PATCH 0/3] dyndbg: add source file name to prefix Thomas Weißschuh
2023-01-30 2:01 ` [PATCH 1/3] dyndbg: constify opt_array Thomas Weißschuh
2023-01-30 2:01 ` [PATCH 2/3] dyndbg: increase PREFIX_SIZE to 128 Thomas Weißschuh
2023-01-30 2:01 ` [PATCH 3/3] dyndbg: add source filename to prefix Thomas Weißschuh
2023-02-03 16:45 ` Jason Baron
2023-02-04 14:49 ` linux
2023-03-22 15:54 ` jim.cromie
2023-03-20 22:13 ` [PATCH 0/3] dyndbg: add source file name " Thomas Weißschuh
2023-06-27 14:30 ` Thomas Weißschuh
2023-06-27 14:47 ` Greg Kroah-Hartman
2023-06-27 14:57 ` Thomas Weißschuh
2023-06-27 15:01 ` Greg Kroah-Hartman [this message]
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=2023062705-foil-playing-b2da@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=thomas@t-8ch.de \
/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