linux-kernel - Re: [PATCH] drivers: mcb: use symbol namespaces

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: <20191016135300.GA302460@kroah.com>
Date:   Wed, 16 Oct 2019 06:53:00 -0700
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Johannes Thumshirn <jthumshirn@...e.de>
Cc:     Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>,
        Michael Moese <mmoese@...e.de>, Jessica Yu <jeyu@...nel.org>
Subject: Re: [PATCH] drivers: mcb: use symbol namespaces

On Wed, Oct 16, 2019 at 03:45:08PM +0200, Johannes Thumshirn wrote:
> On 16/10/2019 14:51, Greg KH wrote:
> > On Wed, Oct 16, 2019 at 12:01:58PM +0200, Johannes Thumshirn wrote:
> >> Now that we have symbol namespaces, use them in MCB to not pollute the
> >> default namespace with MCB internals.
> >>
> >> Signed-off-by: Johannes Thumshirn <jthumshirn@...e.de>
> >> ---
> >>  drivers/gpio/gpio-menz127.c            |  1 +
> >>  drivers/iio/adc/men_z188_adc.c         |  1 +
> >>  drivers/mcb/mcb-core.c                 | 28 ++++++++++++++--------------
> >>  drivers/mcb/mcb-lpc.c                  |  1 +
> >>  drivers/mcb/mcb-parse.c                |  2 +-
> >>  drivers/mcb/mcb-pci.c                  |  1 +
> >>  drivers/tty/serial/8250/8250_men_mcb.c |  1 +
> >>  drivers/tty/serial/men_z135_uart.c     |  1 +
> >>  drivers/watchdog/menz69_wdt.c          |  1 +
> >>  9 files changed, 22 insertions(+), 15 deletions(-)
> > 
> > Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
> Btw do you want me to send it to you again shortly before the merge
> window opens or can you queue it up before?

I can take this now, into my -next tree.  I'll do so later this week
unless you object.

thanks,

greg k-h