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
Subject: Re: [PATCH] staging: most: usb: rename most_usb.ko
Date: Wed, 29 Jul 2020 19:03:13 +0200	[thread overview]
Message-ID: <20200729170313.GA3668028@kroah.com> (raw)
In-Reply-To: <1596040728-3353-1-git-send-email-christian.gromm@microchip.com>

On Wed, Jul 29, 2020 at 06:38:48PM +0200, Christian Gromm wrote:
> To avoid a name conflict when adding the usb module to the
> driver's directory in the stable branch, this patch simply
> renames the kernel object.
> 
> Signed-off-by: Christian Gromm <christian.gromm@microchip.com>
> Reported-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>  drivers/staging/most/usb/{most_usb.ko => most-usb.ko} | Bin
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename drivers/staging/most/usb/{most_usb.ko => most-usb.ko} (100%)
> 
> diff --git a/drivers/staging/most/usb/most_usb.ko b/drivers/staging/most/usb/most-usb.ko
> similarity index 100%
> rename from drivers/staging/most/usb/most_usb.ko
> rename to drivers/staging/most/usb/most-usb.ko

You renamed a binary file???  That is not in the source tree?

No, I mean make the patch move the .c file from staging to the
drivers/most directory and adjust the Kconfig/Makefiles for that
movement.

thanks,

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

  reply	other threads:[~2020-07-29 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 16:38 [PATCH] staging: most: usb: rename most_usb.ko Christian Gromm
2020-07-29 17:03 ` Greg KH [this message]
2020-07-30  8:27   ` Christian.Gromm
2020-07-30  8:57     ` 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=20200729170313.GA3668028@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=christian.gromm@microchip.com \
    --cc=driverdev-devel@linuxdriverproject.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).