linux-kernel - Re: [PATCH 09/12 v3] staging: usbip: edit Kconfig and rename CONFIG options

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: <BANLkTin=sdSp_kpL1SWSxZHBqa20RB3Y-A@mail.gmail.com>
Date:	Wed, 11 May 2011 22:32:51 -0700
From:	matt mooney <mfmooney@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 09/12 v3] staging: usbip: edit Kconfig and rename CONFIG options

On Wed, May 11, 2011 at 10:32 PM, Greg KH <greg@...ah.com> wrote:
> On Wed, May 11, 2011 at 10:17:08PM -0700, mfmooney@...il.com wrote:
>> From: matt mooney <mfm@...eddisk.com>
>>
>> Change modules usbip_common_mod to usbip-core and usbip to usbip-host;
>> edit configuration option help text; rename CONFIG options to use a
>> USBIP prefix and change COMMON to CORE in both the Kconfig and
>> Makefiles; edit the menu entries and the driver descriptions.
>>
>> Signed-off-by: matt mooney <mfm@...eddisk.com>
>> ---
>> I actually change to module names in this patch now, and I had forgot to add that
>> into the commit message.
>
> I'm confused, there really isn't going to be 12 patches here in this new
> series, right?
>
> Care to start numbering them over and send them in a new thread so I can
> figure out what to apply in what order?
>
> thanks,
>
> greg k-h
>

Heh, sorry I didn't know what was easier for you.

-- 
GPG-Key: 9AFE00EA
--
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/