All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: deller@gmx.de, arnd@arndb.de, linux-arch@vger.kernel.org,
	 linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] modules: few of alignment fixes
Date: Sat, 3 Feb 2024 00:20:38 +0900	[thread overview]
Message-ID: <CAK7LNATjKzUVR7DbJqb=yAinJ1YZo8tzwiXA79E9-VrDn11wwg@mail.gmail.com> (raw)
In-Reply-To: <ZbvdbdxOKZ9FUQuC@bombadil.infradead.org>

On Fri, Feb 2, 2024 at 3:05 AM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> On Wed, Jan 31, 2024 at 02:11:44PM -0800, Luis Chamberlain wrote:
> > On Mon, Jan 29, 2024 at 11:26:39AM -0800, Luis Chamberlain wrote:
> > > Masahiro, if there no issues feel free to take this or I can take them in
> > > too via the modules-next tree. Lemme know!
> >
> > I've queued this onto modules-testing to get winder testing [0]
>
> I've moved it to modules-next as I've found no issues.
>
>   Luis


I believe this patch series is wrong.



I thought we agreed that the alignment must be added to
individual asm code, not to the linker script.

I am surprised that you came back to this.







--
Best Regards
Masahiro Yamada

  reply	other threads:[~2024-02-02 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 19:26 [PATCH v2 0/3] modules: few of alignment fixes Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 1/4] selftests: add new kallsyms selftests Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 2/4] modules: Ensure 64-bit alignment on __ksymtab_* sections Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 3/4] vmlinux.lds.h: add missing alignment for symbol CRCs Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 4/4] modules: Add missing entry for __ex_table Luis Chamberlain
2024-01-31 22:11 ` [PATCH v2 0/3] modules: few of alignment fixes Luis Chamberlain
2024-02-01 18:05   ` Luis Chamberlain
2024-02-02 15:20     ` Masahiro Yamada [this message]
2024-02-02 18:23       ` Luis Chamberlain

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='CAK7LNATjKzUVR7DbJqb=yAinJ1YZo8tzwiXA79E9-VrDn11wwg@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=arnd@arndb.de \
    --cc=deller@gmx.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@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.