All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Nicholas Piggin <npiggin@gmail.com>
Cc: linux-modules@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Jessica Yu <jeyu@kernel.org>
Subject: Re: [PATCH v5 0/2] powerpc module arch checks
Date: Thu, 03 Nov 2022 20:35:32 +1100	[thread overview]
Message-ID: <87leoss7mj.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <Y2MEw6BruH3FnYL/@bombadil.infradead.org>

Luis Chamberlain <mcgrof@kernel.org> writes:
> On Mon, Oct 31, 2022 at 10:07:31PM +1000, Nicholas Piggin wrote:
>> Luis if you would be okay for patch 1 to be merged via powerpc or
>> prefer to take it in the module tree (or maybe you object to the
>> code in the first place).
>
> Looks good to me, and nothing on my radar which would cause a conflict
> so happy for you to take it via powerpc or I can take it and apply it
> right away to tricke / get tested on linux-next by tomorrow.
>
> Let me know.

Thanks. I guess it's mostly a nop on other architectures, so probably
makes sense for me to take it.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-modules@vger.kernel.org, Jessica Yu <jeyu@kernel.org>
Subject: Re: [PATCH v5 0/2] powerpc module arch checks
Date: Thu, 03 Nov 2022 20:35:32 +1100	[thread overview]
Message-ID: <87leoss7mj.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <Y2MEw6BruH3FnYL/@bombadil.infradead.org>

Luis Chamberlain <mcgrof@kernel.org> writes:
> On Mon, Oct 31, 2022 at 10:07:31PM +1000, Nicholas Piggin wrote:
>> Luis if you would be okay for patch 1 to be merged via powerpc or
>> prefer to take it in the module tree (or maybe you object to the
>> code in the first place).
>
> Looks good to me, and nothing on my radar which would cause a conflict
> so happy for you to take it via powerpc or I can take it and apply it
> right away to tricke / get tested on linux-next by tomorrow.
>
> Let me know.

Thanks. I guess it's mostly a nop on other architectures, so probably
makes sense for me to take it.

cheers

  reply	other threads:[~2022-11-03  9:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 12:07 [PATCH v5 0/2] powerpc module arch checks Nicholas Piggin
2022-10-31 12:07 ` Nicholas Piggin
2022-10-31 12:07 ` [PATCH v5 1/2] module: add module_elf_check_arch for module-specific checks Nicholas Piggin
2022-10-31 12:07   ` Nicholas Piggin
2022-11-02 23:59   ` Luis Chamberlain
2022-11-02 23:59     ` Luis Chamberlain
2022-10-31 12:07 ` [PATCH v5 2/2] powerpc/64: Add module check for ELF ABI version Nicholas Piggin
2022-10-31 12:07   ` Nicholas Piggin
2022-11-03  8:35   ` Christophe Leroy
2022-11-03  8:35     ` Christophe Leroy
2022-11-07 12:14     ` Nicholas Piggin
2022-11-07 12:14       ` Nicholas Piggin
2022-11-03  0:01 ` [PATCH v5 0/2] powerpc module arch checks Luis Chamberlain
2022-11-03  0:01   ` Luis Chamberlain
2022-11-03  9:35   ` Michael Ellerman [this message]
2022-11-03  9:35     ` Michael Ellerman

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=87leoss7mj.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=jeyu@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mcgrof@kernel.org \
    --cc=npiggin@gmail.com \
    /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.