mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul@pwsan.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Ryo Takakura <takakura@valinux.co.jp>,
	Sunil V L <sunilvl@ventanamicro.com>
Subject: Re: linux-next: manual merge of the pm tree with the risc-v tree
Date: Tue, 17 Sep 2024 10:21:03 +1000	[thread overview]
Message-ID: <20240917102103.0e29172b@canb.auug.org.au> (raw)
In-Reply-To: <20240902121140.51cc49c9@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

Hi all,

On Mon, 2 Sep 2024 12:11:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the pm tree got a conflict in:
> 
>   arch/riscv/include/asm/irq.h
> 
> between commit:
> 
>   f15c21a3de1b ("RISC-V: Enable IPI CPU Backtrace")
> 
> from the risc-v tree and commit:
> 
>   f8619b66bdb1 ("irqchip/riscv-intc: Add ACPI support for AIA")
> 
> from the pm tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc arch/riscv/include/asm/irq.h
> index 8330d16b05b5,7e9a84a005ed..000000000000
> --- a/arch/riscv/include/asm/irq.h
> +++ b/arch/riscv/include/asm/irq.h
> @@@ -12,11 -12,8 +12,13 @@@
>   
>   #include <asm-generic/irq.h>
>   
> + #define INVALID_CONTEXT UINT_MAX
> + 
>  +#ifdef CONFIG_SMP
>  +void arch_trigger_cpumask_backtrace(const cpumask_t *mask, int exclude_cpu);
>  +#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
>  +#endif
>  +
>   void riscv_set_intc_hwnode_fn(struct fwnode_handle *(*fn)(void));
>   
>   struct fwnode_handle *riscv_get_intc_hwnode(void);

This is now a conflict between the risc-v tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-09-17  0:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  2:11 Stephen Rothwell
2024-09-17  0:21 ` Stephen Rothwell [this message]
2026-08-06 13:11 Mark Brown

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=20240917102103.0e29172b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul@pwsan.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=sunilvl@ventanamicro.com \
    --cc=takakura@valinux.co.jp \
    /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

all inboxes | Powered by JetHome®