From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-acpi@vger.kernel.org, timur@codeaurora.org,
cov@codeaurora.org, jcm@redhat.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4] acpi: add support for extended IRQ to PCI link
Date: Tue, 24 Nov 2015 15:05:40 -0500 [thread overview]
Message-ID: <5654C314.7050201@codeaurora.org> (raw)
In-Reply-To: <20151124181150.GA27957@localhost>
On 11/24/2015 1:11 PM, Bjorn Helgaas wrote:
>
> As Andy mentioned, please wrap this text to use more of an 80-column
> line. I fill changelogs to 75 columns (vi textwidth=75), which fits
> perfectly when "git log" inserts 4 leading spaces.
>
will do
>
> These changes are basically all bounds-checking link->irq.possible[i]
> and link->irq.active. What if you put that checking at the point
> where we *initialize* those fields instead, i.e., in
> acpi_pci_link_check_possible() and acpi_pci_link_get_current()? Then
> you'd only have to check each field in one place, and you could easily
> add a message if we see an ID that's too large.
>
I'll post a patch soon.
> I think the current code for ACPI_RESOURCE_TYPE_EXTENDED_IRQ is buggy
> because it silently truncates IDs to 8 bits.
>
> Bjorn
>
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-11-24 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 3:13 [PATCH V4] acpi: add support for extended IRQ to PCI link Sinan Kaya
2015-11-21 18:44 ` Sinan Kaya
2015-11-24 18:11 ` Bjorn Helgaas
2015-11-24 20:05 ` Sinan Kaya [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=5654C314.7050201@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=cov@codeaurora.org \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=timur@codeaurora.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