driverdev-devel.linuxdriverproject.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Gromm <christian.gromm@microchip.com>
Cc: driverdev-devel@linuxdriverproject.org, linux-usb@vger.kernel.org
Subject: Re: [RESEND PATCH v5] drivers: most: add USB adapter driver
Date: Wed, 29 Jul 2020 16:27:15 +0200	[thread overview]
Message-ID: <20200729142715.GA3343116@kroah.com> (raw)
In-Reply-To: <1595838646-12674-1-git-send-email-christian.gromm@microchip.com>

On Mon, Jul 27, 2020 at 10:30:46AM +0200, Christian Gromm wrote:
> This patch adds the usb driver source file most_usb.c and
> modifies the Makefile and Kconfig accordingly.
> 
> Signed-off-by: Christian Gromm <christian.gromm@microchip.com>

Sorry for the long delay in getting to this.

This looks good to me, but I tried to apply it to my usb tree, and of
course I get the following build error:
	error: the following would cause module name conflict:
	  drivers/staging/most/usb/most_usb.ko
	  drivers/most/most_usb.ko

So, can you just send a "rename the file" patch that I can apply against
my staging-next branch and I will take it through there so that there
are no conflicts like this?

thanks,

greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  parent reply	other threads:[~2020-07-29 14:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  8:30 [RESEND PATCH v5] drivers: most: add USB adapter driver Christian Gromm
2020-07-27 14:59 ` Randy Dunlap
2020-07-28  7:19   ` Christian.Gromm
2020-07-29 14:27 ` Greg KH [this message]
2020-07-29 14:53   ` Christian.Gromm
2020-07-29 14:57     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2020-07-01 11:46 Christian Gromm

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=20200729142715.GA3343116@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=christian.gromm@microchip.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=linux-usb@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).