linux-kernel - [PATCH 0/5] toshiba_acpi: Clean file plus some function renames

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1423637040-6813-1-git-send-email-coproscefalo@gmail.com>
Date:	Tue, 10 Feb 2015 23:43:55 -0700
From:	Azael Avalos <coproscefalo@...il.com>
To:	Darren Hart <dvhart@...radead.org>,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	Azael Avalos <coproscefalo@...il.com>
Subject: [PATCH 0/5] toshiba_acpi: Clean file plus some function renames

These patches are simply "cleaning" the file, making it more readable
and in the process, make it comply according to coding style.

--->8---
Darren,

I'm sending these patches now and let you decide if you want them for
3.20 as the merge window is still open or queue them up for 3.21 :-)
---8<---

Azael Avalos (5):
  toshiba_acpi: Clean file according to coding style
  Documentation/ABI: Add file describing the sysfs entries for
    toshiba_acpi
  toshiba_acpi: Move sysfs function and struct declarations further down
  toshiba_acpi: Drop the toshiba_ prefix from sysfs function names
  toshiba_acpi: Make use of DEVICE_ATTR_{RO, RW} macros

 .../ABI/testing/sysfs-driver-toshiba_acpi          | 114 +++++++
 drivers/platform/x86/toshiba_acpi.c                | 344 ++++++++-------------
 2 files changed, 237 insertions(+), 221 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-driver-toshiba_acpi

-- 
2.2.2

--
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/