Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Karthikeyan KS <karthiproffesional@gmail.com>
Cc: joel@jms.id.au, andrew@aj.id.au, Kees Cook <kees@kernel.org>,
	 linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org,  linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH v6] soc: aspeed: lpc-snoop: Fix usercopy overflow in snoop_file_read
Date: Thu, 02 Jul 2026 09:55:23 +0930	[thread overview]
Message-ID: <33cf45f92e4aa2ca985501807c3e4f74e1a10032.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260701171506.338614-1-karthiproffesional@gmail.com>

Hi,

On Wed, 2026-07-01 at 17:15 +0000, Karthikeyan KS wrote:
> Hi Andrew,
> 
> Just following up, it's been about two weeks since I shared the
> hardware validation results. I believe I've addressed the questions
> raised in the thread, but please let me know if there's anything
> else you'd like me to do.

Nothing further required on your part. I intend to apply it, however am
working through some other priorities.

Thanks,

Andrew


  reply	other threads:[~2026-07-02  0:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c3d474a1ec807e686c0b7ac70cc75f86898aee99.camel@codeconstruct.com.au>
2026-05-23 17:35 ` [PATCH v2] soc: aspeed: lpc-snoop: Fix usercopy overflow in snoop_file_read Karthikeyan KS
2026-05-27  3:53   ` Andrew Jeffery
2026-05-27 17:59     ` [PATCH v3] " Karthikeyan KS
2026-05-28  2:39       ` Andrew Jeffery
2026-06-01 12:52         ` [PATCH v4] " Karthikeyan KS
2026-06-10  2:26           ` Andrew Jeffery
2026-06-10 17:23             ` [PATCH v5] " Karthikeyan KS
2026-06-11  2:50               ` Andrew Jeffery
     [not found]                 ` <CAP_JKPu9MTpMUZmg9BY3sxGhmBzgR0E6HnvAT7sQjVUpQp0dSQ@mail.gmail.com>
2026-06-12  0:39                   ` Andrew Jeffery
2026-06-11 18:08             ` Karthikeyan KS
2026-06-12 19:07             ` [PATCH v6] " Karthikeyan KS
2026-06-16  0:20               ` Andrew Jeffery
2026-06-16  7:30             ` Karthikeyan KS
2026-06-17  0:44               ` Andrew Jeffery
2026-06-17 13:10             ` Karthikeyan KS
2026-06-18  0:44               ` Andrew Jeffery
2026-06-20 13:11             ` Karthikeyan KS
2026-07-01 17:15             ` Karthikeyan KS
2026-07-02  0:25               ` Andrew Jeffery [this message]
2026-07-02 17:35             ` Karthikeyan KS

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=33cf45f92e4aa2ca985501807c3e4f74e1a10032.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=karthiproffesional@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox