public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Oleg Nesterov <oleg@redhat.com>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Fix MAX_REG_OFFSET and remove zero-length struct member
Date: Fri, 18 Apr 2025 09:57:50 +0200	[thread overview]
Message-ID: <aAIF_kEFlOOVNDaE@alpha.franken.de> (raw)
In-Reply-To: <20250417174712.69292-2-thorsten.blum@linux.dev>

On Thu, Apr 17, 2025 at 07:47:13PM +0200, Thorsten Blum wrote:
> Remove the unnecessary zero-length struct member '__last' and fix
> MAX_REG_OFFSET to point to the last register in 'pt_regs'.
> 
> Fixes: 40e084a506eba ("MIPS: Add uprobes support.")

what does it fix ?

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2025-04-18  8:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 17:47 [PATCH v2] MIPS: Fix MAX_REG_OFFSET and remove zero-length struct member Thorsten Blum
2025-04-18  7:57 ` Thomas Bogendoerfer [this message]
2025-04-18 10:06   ` Thorsten Blum
2025-04-18 10:36     ` Maciej W. Rozycki
2025-04-18 11:05       ` Thorsten Blum
2025-04-18 12:44         ` Maciej W. Rozycki
2025-04-18 13:38           ` Thorsten Blum
2025-04-18 15:14             ` Maciej W. Rozycki
2025-04-18 20:18               ` Thorsten Blum
2025-04-18 20:21                 ` Thorsten Blum
2025-04-19  2:56                   ` Huacai Chen
2025-04-19 10:35                     ` Thorsten Blum
2025-04-27  7:12                   ` Thomas Bogendoerfer
2025-04-27 16:22             ` Thomas Bogendoerfer

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=aAIF_kEFlOOVNDaE@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=oleg@redhat.com \
    --cc=thorsten.blum@linux.dev \
    /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