linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Hans de Goede <hdegoede@redhat.com>, Mark Gross <markgross@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Patil Rajesh Reddy" <Patil.Reddy@amd.com>,
	"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>
Subject: linux-next: manual merge of the drivers-x86 tree with Linus' tree
Date: Fri, 8 Mar 2024 13:19:34 +1100	[thread overview]
Message-ID: <20240308131934.298896a6@canb.auug.org.au> (raw)

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

Hi all,

Today's linux-next merge of the drivers-x86 tree got a conflict in:

  drivers/platform/x86/amd/pmf/core.c

between commit:

  11e298f3548a ("platform/x86/amd/pmf: Fix TEE enact command failure after suspend and resume")

from Linus' tree and commit:

  6eacd474b8be ("platform/x86/amd/pmf: Add support to notify sbios heart beat event")

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.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/platform/x86/amd/pmf/core.c
index 4f734e049f4a,53c0f61e5c5f..000000000000
--- a/drivers/platform/x86/amd/pmf/core.c
+++ b/drivers/platform/x86/amd/pmf/core.c
@@@ -296,9 -297,11 +297,12 @@@ static int amd_pmf_suspend_handler(stru
  {
  	struct amd_pmf_dev *pdev = dev_get_drvdata(dev);
  
 -	kfree(pdev->buf);
 +	if (pdev->smart_pc_enabled)
 +		cancel_delayed_work_sync(&pdev->pb_work);
  
+ 	if (is_apmf_func_supported(pdev, APMF_FUNC_SBIOS_HEARTBEAT_V2))
+ 		amd_pmf_notify_sbios_heartbeat_event_v2(pdev, ON_SUSPEND);
+ 
  	return 0;
  }
  
@@@ -313,9 -316,9 +317,12 @@@ static int amd_pmf_resume_handler(struc
  			return ret;
  	}
  
+ 	if (is_apmf_func_supported(pdev, APMF_FUNC_SBIOS_HEARTBEAT_V2))
+ 		amd_pmf_notify_sbios_heartbeat_event_v2(pdev, ON_RESUME);
+ 
 +	if (pdev->smart_pc_enabled)
 +		schedule_delayed_work(&pdev->pb_work, msecs_to_jiffies(2000));
 +
  	return 0;
  }
  

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

             reply	other threads:[~2024-03-08  2:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  2:19 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-08  2:34 linux-next: manual merge of the drivers-x86 tree with Linus' tree Stephen Rothwell
2024-03-01  3:14 Stephen Rothwell
2024-02-08  1:57 Stephen Rothwell
2024-01-02  2:30 Stephen Rothwell
2018-10-29  3:29 Stephen Rothwell
2018-10-29  9:34 ` Andy Shevchenko
2016-01-15  1:56 Stephen Rothwell
2015-06-02  6:07 Stephen Rothwell
2015-06-03  3:27 ` Darren Hart
2015-06-03  4:04   ` Stephen Rothwell
2012-05-31  2:06 Stephen Rothwell
2011-04-08  5:26 Stephen Rothwell
2011-03-24  2:48 Stephen Rothwell
2011-03-24  2:52 ` Matthew Garrett
2010-08-25  1:22 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=20240308131934.298896a6@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Patil.Reddy@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=markgross@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).