linux-kernel - Re: [PATCH 2/4] Rename ramzswap files to zram

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C09F5F0.6020902@vflare.org>
Date:	Sat, 05 Jun 2010 12:30:00 +0530
From:	Nitin Gupta <ngupta@...are.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Greg KH <greg@...ah.com>, Pekka Enberg <penberg@...helsinki.fi>,
	Minchan Kim <minchan.kim@...il.com>, Ed Tomlinson <edt@....ca>,
	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	Cyp <cyp561@...il.com>, driverdev <devel@...verdev.osuosl.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] Rename ramzswap files to zram

On 06/05/2010 01:02 AM, Andrew Morton wrote:
> On Tue,  1 Jun 2010 13:31:24 +0530
> Nitin Gupta <ngupta@...are.org> wrote:
> 
>> Related changes:
>>  - Modify revelant Kconfig and Makefile accordingly.
>>  - Change include filenames in code.
>>  - Remove dependency on CONFIG_SWAP in Kconfig as zram usage
>> is no longer limited to swap disks.
>>
>> Signed-off-by: Nitin Gupta <ngupta@...are.org>
>> ---
>>  drivers/staging/Kconfig                            |    2 +-
>>  drivers/staging/Makefile                           |    2 +-
>>  drivers/staging/ramzswap/Kconfig                   |   21 ---------------
>>  drivers/staging/ramzswap/Makefile                  |    3 --
>>  drivers/staging/zram/Kconfig                       |   28 ++++++++++++++++++++
>>  drivers/staging/zram/Makefile                      |    3 ++
>>  drivers/staging/{ramzswap => zram}/xvmalloc.c      |    0
>>  drivers/staging/{ramzswap => zram}/xvmalloc.h      |    0
>>  drivers/staging/{ramzswap => zram}/xvmalloc_int.h  |    0
>>  .../{ramzswap/ramzswap.txt => zram/zram.txt}       |    0
>>  .../{ramzswap/ramzswap_drv.c => zram/zram_drv.c}   |    2 +-
>>  .../{ramzswap/ramzswap_drv.h => zram/zram_drv.h}   |    2 +-
>>  .../ramzswap_ioctl.h => zram/zram_ioctl.h}         |    0
>>  13 files changed, 35 insertions(+), 28 deletions(-)
>>  delete mode 100644 drivers/staging/ramzswap/Kconfig
>>  delete mode 100644 drivers/staging/ramzswap/Makefile
>>  create mode 100644 drivers/staging/zram/Kconfig
>>  create mode 100644 drivers/staging/zram/Makefile
>>  rename drivers/staging/{ramzswap => zram}/xvmalloc.c (100%)
>>  rename drivers/staging/{ramzswap => zram}/xvmalloc.h (100%)
>>  rename drivers/staging/{ramzswap => zram}/xvmalloc_int.h (100%)
>>  rename drivers/staging/{ramzswap/ramzswap.txt => zram/zram.txt} (100%)
>>  rename drivers/staging/{ramzswap/ramzswap_drv.c => zram/zram_drv.c} (99%)
>>  rename drivers/staging/{ramzswap/ramzswap_drv.h => zram/zram_drv.h} (99%)
>>  rename drivers/staging/{ramzswap/ramzswap_ioctl.h => zram/zram_ioctl.h} (100%)
> 
> This is a git-specific thing and doesn't do anything useful for people
> who use plain-old-patch(1) (eg: Greg and me).
> 
> Obviously we can manually type in the commands and put the massive
> file-moving diff together, but it's a bit of a pain.
> 
> Maybe Greg has some magic automated way of turning these into regular
> patches, but I don't.
> 
> 

I used 'git-format-patch -M' as it should be easier to review
(as suggested by Arnd).

Anyways, I'm was not sure if I should be sending normal (non-git-specific)
version of these patches again. So, uploaded them here instead:

single monolithic patch:
http://compcache.googlecode.com/hg/sub-projects/mainline/zramv2_2.6.35-rc1.patch

or, if you prefer patch series:
http://compcache.googlecode.com/hg/sub-projects/mainline/zramv2_patch_series

Thanks,
Nitin



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