Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Darren Hart <dvhart@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Gayatri Kammela <gayatri.kammela@intel.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@suse.de>
Subject: Re: linux-next: manual merge of the drivers-x86 tree with the tip tree
Date: Thu, 26 Mar 2020 10:47:26 +0200
Message-ID: <CAHp75VdCf7HRy2BBHw9---p+-eSt0cN1jRaL9D4U_7MpmG5cWw@mail.gmail.com> (raw)
In-Reply-To: <20200326150523.02c4ec48@canb.auug.org.au>

On Thu, Mar 26, 2020 at 6:05 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the drivers-x86 tree got a conflict in:
>
>   drivers/platform/x86/intel_pmc_core.c
>
> between commit:
>
>   a69b3b1d4cf0 ("platform/x86: Convert to new CPU match macros")
>
> from the tip tree and commit:
>
>   16292bed9c56 ("platform/x86: intel_pmc_core: Add Atom based Jasper Lake (JSL) platform support")
>
> from the drivers-x86 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.
>

Looks correct to me, i.e. new macro for code in PDx86.
Thank you, Stephen!

> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/platform/x86/intel_pmc_core.c
> index 3df33ff50faa,d265cd5b1f45..000000000000
> --- a/drivers/platform/x86/intel_pmc_core.c
> +++ b/drivers/platform/x86/intel_pmc_core.c
> @@@ -871,18 -1144,19 +1144,19 @@@ static inline void pmc_core_dbgfs_unreg
>   #endif /* CONFIG_DEBUG_FS */
>
>   static const struct x86_cpu_id intel_pmc_core_ids[] = {
>  -      INTEL_CPU_FAM6(SKYLAKE_L, spt_reg_map),
>  -      INTEL_CPU_FAM6(SKYLAKE, spt_reg_map),
>  -      INTEL_CPU_FAM6(KABYLAKE_L, spt_reg_map),
>  -      INTEL_CPU_FAM6(KABYLAKE, spt_reg_map),
>  -      INTEL_CPU_FAM6(CANNONLAKE_L, cnp_reg_map),
>  -      INTEL_CPU_FAM6(ICELAKE_L, icl_reg_map),
>  -      INTEL_CPU_FAM6(ICELAKE_NNPI, icl_reg_map),
>  -      INTEL_CPU_FAM6(COMETLAKE, cnp_reg_map),
>  -      INTEL_CPU_FAM6(COMETLAKE_L, cnp_reg_map),
>  -      INTEL_CPU_FAM6(TIGERLAKE_L, tgl_reg_map),
>  -      INTEL_CPU_FAM6(TIGERLAKE, tgl_reg_map),
>  -      INTEL_CPU_FAM6(ATOM_TREMONT, tgl_reg_map),
>  -      INTEL_CPU_FAM6(ATOM_TREMONT_L, tgl_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(SKYLAKE_L,           &spt_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(SKYLAKE,             &spt_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(KABYLAKE_L,          &spt_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(KABYLAKE,            &spt_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(CANNONLAKE_L,        &cnp_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(ICELAKE_L,           &icl_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(ICELAKE_NNPI,        &icl_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(COMETLAKE,           &cnp_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(COMETLAKE_L,         &cnp_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(TIGERLAKE_L,         &tgl_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(TIGERLAKE,           &tgl_reg_map),
>  +      X86_MATCH_INTEL_FAM6_MODEL(ATOM_TREMONT,        &tgl_reg_map),
> ++      X86_MATCH_INTEL_FAM6_MODEL(ATOM_TREMONT_L,      &tgl_reg_map),
>         {}
>   };
>


-- 
With Best Regards,
Andy Shevchenko

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  4:05 Stephen Rothwell
2020-03-26  8:47 ` Andy Shevchenko [this message]
2020-04-01  3:14 ` Stephen Rothwell
2020-04-01  6:49   ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2018-10-08  3:48 Stephen Rothwell
2018-10-08 10:55 ` Andy Shevchenko
2018-10-08  3:44 Stephen Rothwell
2018-10-08 10:55 ` Andy Shevchenko
2012-03-13  6:51 Stephen Rothwell

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=CAHp75VdCf7HRy2BBHw9---p+-eSt0cN1jRaL9D4U_7MpmG5cWw@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=bp@suse.de \
    --cc=dvhart@infradead.org \
    --cc=gayatri.kammela@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git