From: Greg KH <gregkh@linuxfoundation.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Michael Moese <mmoese@suse.de>, Jessica Yu <jeyu@kernel.org>
Subject: Re: [PATCH] drivers: mcb: use symbol namespaces
Date: Wed, 16 Oct 2019 06:53:00 -0700 [thread overview]
Message-ID: <20191016135300.GA302460@kroah.com> (raw)
In-Reply-To: <48f87640-d277-fdb6-3d6e-3f88b7623f22@suse.de>
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@suse.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@linuxfoundation.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
next prev parent reply other threads:[~2019-10-16 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 10:01 [PATCH] drivers: mcb: use symbol namespaces Johannes Thumshirn
2019-10-16 11:30 ` Jessica Yu
2019-10-16 11:32 ` Michael Moese
2019-10-16 12:51 ` Greg KH
2019-10-16 13:45 ` Johannes Thumshirn
2019-10-16 13:53 ` Greg KH [this message]
2019-10-17 7:05 ` Johannes Thumshirn
2019-10-29 9:20 ` Johannes Thumshirn
2019-11-03 18:54 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191016135300.GA302460@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mmoese@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox