linux-kernel - Re: [PATCH v2] {tty: serial, nand: onenand}: samsung: rename to fix build warning

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: <1505628642.90849.1574081270290.JavaMail.zimbra@nod.at>
Date:   Mon, 18 Nov 2019 13:47:50 +0100 (CET)
From:   Richard Weinberger <richard@....at>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Sudip Mukherjee <sudipm.mukherjee@...il.com>,
        Kyungmin Park <kyungmin.park@...sung.com>,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Vignesh Raghavendra <vigneshr@...com>,
        Jiri Slaby <jslaby@...e.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-mtd <linux-mtd@...ts.infradead.org>,
        linux-serial@...r.kernel.org
Subject: Re: [PATCH v2] {tty: serial, nand: onenand}: samsung: rename to fix
 build warning

----- Ursprüngliche Mail -----
>> I was not sure if this should have been two different patch, but since
>> this will be fixing the same problem so it seems its better to have them
>> in a single patch.
>> 
>>  drivers/mtd/nand/onenand/Makefile                     | 2 +-
>>  drivers/mtd/nand/onenand/{samsung.c => samsung_mtd.c} | 0
>>  drivers/tty/serial/Makefile                           | 2 +-
>>  drivers/tty/serial/{samsung.c => samsung_tty.c}       | 0
>>  4 files changed, 2 insertions(+), 2 deletions(-)
>>  rename drivers/mtd/nand/onenand/{samsung.c => samsung_mtd.c} (100%)
>>  rename drivers/tty/serial/{samsung.c => samsung_tty.c} (100%)
> 
> I can take this in the tty tree if the mtd maintainer gives an ack for
> it...

Acked-by: Richard Weinberger <richard@....at>

Thanks,
//richard