All of lore.kernel.org
 help / color / mirror / Atom feed
From: dmukhin@ford.com
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: dmukhin@ford.com, xen-devel@lists.xenproject.org,
	andrew.cooper3@citrix.com, anthony.perard@vates.tech,
	jbeulich@suse.com, julien@xen.org, michal.orzel@amd.com,
	roger.pau@citrix.com, sstabellini@kernel.org,
	Daniel Smith <dpsmith@apertussolutions.com>,
	"Andryuk, Jason" <Jason.Andryuk@amd.com>
Subject: Re: [PATCH v6 0/6] argo: few log fixes
Date: Mon, 8 Jun 2026 18:28:06 -0700	[thread overview]
Message-ID: <aidsJvlM/OtymlJJ@kraken> (raw)
In-Reply-To: <CACMJ4GZW26MGYr9RbCw=tO9rvrpL1u-PAHG9BaFvyg6RnDDfAQ@mail.gmail.com>

Hi all,

On Mon, Jun 08, 2026 at 10:49:55PM +0100, Christopher Clark wrote:
> On Thu, Jun 4, 2026 at 10:49 PM <dmukhin@ford.com> wrote:
> >
> > This series corrects Argo module tracing.
> 
> This series has been committed to staging.
> 
> The maintainers were not CC'd on the series, and did not provide an ack.

Sorry, I did not mean to overrule anything or violate the existing process.

I posted the series as an attempt to resolve the log spam reported internally.

I also appreciate the time everyone involved spent reviewing and providing
feedback on this small series.

> 
> Patch 1 is rejected as an inappropriate change.
> 
> Therefore it needs reverting.
> 
> > Patch 1 lowers the verbosity of a spammy log message.
> 
> Please see the review comment provided by Daniel on the v3 version.
> 
> thanks
> 
> Christopher
> 


--
Denis


      parent reply	other threads:[~2026-06-09  1:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 21:49 [PATCH v6 0/6] argo: few log fixes dmukhin
2026-06-04 21:49 ` [PATCH v6 1/6] argo: lower level of noisy connection-refused log dmukhin
2026-06-04 21:49 ` [PATCH v6 2/6] argo: correct logline in ring_unmap() dmukhin
2026-06-04 21:49 ` [PATCH v6 3/6] argo: drop argo prefix from argo_dprintk() calls dmukhin
2026-06-04 21:49 ` [PATCH v6 4/6] argo: fixup argo_dprintk() dmukhin
2026-06-04 21:49 ` [PATCH v6 5/6] argo: introduce CONFIG_ARGO_DEBUG dmukhin
2026-06-04 21:49 ` [PATCH v6 6/6] automation: enable Argo debugging in CI dmukhin
2026-06-05  6:23 ` [PATCH v6 0/6] argo: few log fixes Jan Beulich
2026-06-05 17:24   ` dmukhin
2026-06-08 21:49 ` Christopher Clark
2026-06-08 22:02   ` Andrew Cooper
2026-06-08 22:03   ` Jason Andryuk
2026-06-09  1:28   ` dmukhin [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=aidsJvlM/OtymlJJ@kraken \
    --to=dmukhin@ford.com \
    --cc=Jason.Andryuk@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=christopher.w.clark@gmail.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.