From: Joerg Roedel <joro@8bytes.org>
To: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Wan Zongshun <Vincent.Wan-5C7GfCeVMHo@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] iommu/amd: Signedness bug in acpihid_device_group()
Date: Mon, 11 Apr 2016 14:11:32 +0000 [thread overview]
Message-ID: <20160411141132.GP17838@8bytes.org> (raw)
In-Reply-To: <20160411071446.GB10739@mwanda>
On Mon, Apr 11, 2016 at 10:14:46AM +0300, Dan Carpenter wrote:
> "devid" needs to be signed for the error handling to work.
>
> Fixes:b097d11a0fa3f ('iommu/amd: Manage iommu_group for ACPI HID devices')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Wan Zongshun <Vincent.Wan-5C7GfCeVMHo@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] iommu/amd: Signedness bug in acpihid_device_group()
Date: Mon, 11 Apr 2016 16:11:32 +0200 [thread overview]
Message-ID: <20160411141132.GP17838@8bytes.org> (raw)
In-Reply-To: <20160411071446.GB10739@mwanda>
On Mon, Apr 11, 2016 at 10:14:46AM +0300, Dan Carpenter wrote:
> "devid" needs to be signed for the error handling to work.
>
> Fixes:b097d11a0fa3f ('iommu/amd: Manage iommu_group for ACPI HID devices')
> Signed-off-by: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Wan Zongshun <Vincent.Wan@amd.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] iommu/amd: Signedness bug in acpihid_device_group()
Date: Mon, 11 Apr 2016 16:11:32 +0200 [thread overview]
Message-ID: <20160411141132.GP17838@8bytes.org> (raw)
In-Reply-To: <20160411071446.GB10739@mwanda>
On Mon, Apr 11, 2016 at 10:14:46AM +0300, Dan Carpenter wrote:
> "devid" needs to be signed for the error handling to work.
>
> Fixes:b097d11a0fa3f ('iommu/amd: Manage iommu_group for ACPI HID devices')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks.
next prev parent reply other threads:[~2016-04-11 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 7:14 [patch] iommu/amd: Signedness bug in acpihid_device_group() Dan Carpenter
2016-04-11 7:14 ` Dan Carpenter
2016-04-11 7:14 ` Dan Carpenter
2016-04-11 7:22 ` Wan, Vincent
2016-04-11 7:22 ` Wan, Vincent
2016-04-11 7:22 ` Wan, Vincent
2016-04-11 14:11 ` Joerg Roedel [this message]
2016-04-11 14:11 ` Joerg Roedel
2016-04-11 14:11 ` Joerg Roedel
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=20160411141132.GP17838@8bytes.org \
--to=joro@8bytes.org \
--cc=Vincent.Wan-5C7GfCeVMHo@public.gmane.org \
--cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.