All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] arm64: KVM: Bump debugging information print down to KERN_DEBUG
Date: Fri, 18 Jun 2021 09:23:49 +0100	[thread overview]
Message-ID: <YMxYFbuC4Ka1PNDb@dell> (raw)
In-Reply-To: <162396615830.1467937.16143448603491809431.b4-ty@kernel.org>

On Thu, 17 Jun 2021, Will Deacon wrote:

> On Thu, 17 Jun 2021 08:30:59 +0100, Lee Jones wrote:
> > This sort of information is only generally useful when debugging.
> > 
> > No need to have these sprinkled through the kernel log otherwise.
> 
> Not sure why this has "KVM" in the subject, so I replaced it with "smp".

Mea culpa.  Looks like I stole it from the wrong:

  `git log --oneline -- arch/arm64/kernel/smp.c`

> Applied to arm64 (for-next/misc), thanks!
> 
> [1/1] arm64: smp: Bump debugging information print down to KERN_DEBUG
>       https://git.kernel.org/arm64/c/cf814bcfa1e6
> 
> Cheers,

Thanking you.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] arm64: KVM: Bump debugging information print down to KERN_DEBUG
Date: Fri, 18 Jun 2021 09:23:49 +0100	[thread overview]
Message-ID: <YMxYFbuC4Ka1PNDb@dell> (raw)
In-Reply-To: <162396615830.1467937.16143448603491809431.b4-ty@kernel.org>

On Thu, 17 Jun 2021, Will Deacon wrote:

> On Thu, 17 Jun 2021 08:30:59 +0100, Lee Jones wrote:
> > This sort of information is only generally useful when debugging.
> > 
> > No need to have these sprinkled through the kernel log otherwise.
> 
> Not sure why this has "KVM" in the subject, so I replaced it with "smp".

Mea culpa.  Looks like I stole it from the wrong:

  `git log --oneline -- arch/arm64/kernel/smp.c`

> Applied to arm64 (for-next/misc), thanks!
> 
> [1/1] arm64: smp: Bump debugging information print down to KERN_DEBUG
>       https://git.kernel.org/arm64/c/cf814bcfa1e6
> 
> Cheers,

Thanking you.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-18  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  7:30 [PATCH 1/1] arm64: KVM: Bump debugging information print down to KERN_DEBUG Lee Jones
2021-06-17  7:30 ` Lee Jones
2021-06-17 22:38 ` Will Deacon
2021-06-17 22:38   ` Will Deacon
2021-06-18  8:23   ` Lee Jones [this message]
2021-06-18  8:23     ` Lee Jones

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=YMxYFbuC4Ka1PNDb@dell \
    --to=lee.jones@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@kernel.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.