linux-kernel - Re: [PATCH v4] aerdrv: Move cper_print_aer() call out of interrupt context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+8MBbK8FNDtKrTAsTKKNUQqkNQ_R0TGTNC3KSeDW4ASeUZ7Xw@mail.gmail.com>
Date:	Thu, 30 May 2013 11:12:57 -0700
From:	Tony Luck <tony.luck@...il.com>
To:	Lance Ortiz <lance.ortiz@...com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>, lance_ortiz@...mail.com,
	Liu Jiang <jiang.liu@...wei.com>,
	Borislav Petkov <bp@...en8.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	linux-pci@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] aerdrv: Move cper_print_aer() call out of interrupt context

Ok - grabbed this version. Will see if I can tempt Linus with a "please pull"
tomorrow (when the commit is suitably aged).

By the way ... this meta-commit description:

> v2 - Re-worded header text.  Removed prefix arg from cper_print_aer().
>      Added TODO message in cper_print_aer().
> v3 - Changed type of u8* to struct aer_capability_regs* in the code
>      to avoid too much casting based on comment from Bjorn Helgaas.
> v4 - Removed TODO message.  Does not have to do with what this patch
>      is trying to fix.

belongs *after* the "---" past the sign-off & Acks ... then "git am" will
drop it from the commit message automatically

-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/