X86 platform drivers
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Julian Winkler <julian.winkler1@web.de>,
	platform-driver-x86@vger.kernel.org,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] intel_scu_pcidrv: add back PCI id for Medfield
Date: Tue, 25 Apr 2023 17:03:26 +0200	[thread overview]
Message-ID: <794e914d-6b63-0da9-4d3c-00b383bb4e87@redhat.com> (raw)
In-Reply-To: <20230416154932.6579-1-julian.winkler1@web.de>

Hi Julian,

On 4/16/23 17:49, Julian Winkler wrote:
> This id was removed in b47018a778c1a18cbc98b4a11936dec4f8c4bb7b, saying it
> is only used on Moorestown, but apparently the same id is also used on
> Medfield.
> 
> Tested on the Medfield based Motorola RAZR i smartphone.
> 
> Signed-off-by: Julian Winkler <julian.winkler1@web.de>

Thank you for your patch, I've applied this patch to my review-hans 
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans

Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.

Patches which are added to review-hans now are intended for
the next rc1. This branch will get rebased to the next rc1 when
it is out and after the rebasing the contents of review-hans
will be pushed to the platform-drivers-x86/for-next branch.

Regards,

Hans






> ---
>  drivers/platform/x86/intel_scu_pcidrv.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/platform/x86/intel_scu_pcidrv.c b/drivers/platform/x86/intel_scu_pcidrv.c
> index 80abc708e4f2..d904fad499aa 100644
> --- a/drivers/platform/x86/intel_scu_pcidrv.c
> +++ b/drivers/platform/x86/intel_scu_pcidrv.c
> @@ -34,6 +34,7 @@ static int intel_scu_pci_probe(struct pci_dev *pdev,
>  
>  static const struct pci_device_id pci_ids[] = {
>  	{ PCI_VDEVICE(INTEL, 0x080e) },
> +	{ PCI_VDEVICE(INTEL, 0x082a) },
>  	{ PCI_VDEVICE(INTEL, 0x08ea) },
>  	{ PCI_VDEVICE(INTEL, 0x0a94) },
>  	{ PCI_VDEVICE(INTEL, 0x11a0) },


      parent reply	other threads:[~2023-04-25 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 15:49 [PATCH] intel_scu_pcidrv: add back PCI id for Medfield Julian Winkler
2023-04-17 10:11 ` Hans de Goede
2023-04-17 10:16   ` Andy Shevchenko
2023-04-17 13:02     ` Julian Winkler
2023-04-25  9:03       ` Hans de Goede
2023-04-27  7:36         ` Julian Winkler
2023-04-25 19:02       ` Andy Shevchenko
2023-04-27  8:06         ` Julian Winkler
2023-04-27 10:33           ` Andy Shevchenko
2023-04-25 15:03 ` Hans de Goede [this message]

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=794e914d-6b63-0da9-4d3c-00b383bb4e87@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=julian.winkler1@web.de \
    --cc=mika.westerberg@linux.intel.com \
    --cc=platform-driver-x86@vger.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