From: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
To: mika.westerberg@linux.intel.com
Cc: YehezkelShB@gmail.com, andreas.noever@gmail.com,
atharvatiwarilinuxdev@gmail.com, bhelgaas@google.com,
bp@alien8.de, dave.hansen@linux.intel.com,
feng.tang@linux.alibaba.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-usb@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
lukas@wunner.de, mahesh@linux.ibm.com, mingo@redhat.com,
oohall@gmail.com, sathyanarayanan.kuppuswamy@linux.intel.com,
tglx@linutronix.de, westeri@kernel.org, x86@kernel.org
Subject: Re: [PATCH v4] PCI/portdev: Disable AER for Titan Ridge 4C 2018
Date: Fri, 9 Jan 2026 11:06:05 +0000 [thread overview]
Message-ID: <20260109110607.2971-1-atharvatiwarilinuxdev@gmail.com> (raw)
In-Reply-To: <20260109100840.GV2275908@black.igk.intel.com>
I dont test it, but I do review the code and fix the issues.
For example:
Using DECLARE_PCI_FIXUP_FINAL instead of DECLARE_PCI_FIXUP_EARLY is wrong
because DECLARE_PCI_FIXUP_FINAL runs after PCIe is initialized.
If i cant install linux, I can’t test it—that’s why there are multiple
revisions, each fixing issues found by code review.
next prev parent reply other threads:[~2026-01-09 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 8:25 [PATCH v4] PCI/portdev: Disable AER for Titan Ridge 4C 2018 Atharva Tiwari
2026-01-08 9:53 ` Mika Westerberg
2026-01-08 10:33 ` Atharva Tiwari
2026-01-08 11:37 ` Mika Westerberg
2026-01-08 14:18 ` Atharva Tiwari
2026-01-09 6:57 ` Mika Westerberg
2026-01-09 8:14 ` Atharva Tiwari
2026-01-09 10:08 ` Mika Westerberg
2026-01-09 11:06 ` Atharva Tiwari [this message]
2026-01-08 10:37 ` Atharva Tiwari
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=20260109110607.2971-1-atharvatiwarilinuxdev@gmail.com \
--to=atharvatiwarilinuxdev@gmail.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=feng.tang@linux.alibaba.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mingo@redhat.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=westeri@kernel.org \
--cc=x86@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