All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Frank Wunderlich <linux@fw-web.de>
Cc: linux-mediatek@lists.infradead.org,
	Frank Wunderlich <frank-w@public-files.de>,
	Bin Liu <b-liu@ti.com>, Matthias Brugger <matthias.bgg@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	David Miller <davem@davemloft.net>,
	DENG Qingfang <dqfext@gmail.com>
Subject: Re: [PATCH] musb: mediatek: rename driver
Date: Fri, 30 Apr 2021 14:54:03 +0200	[thread overview]
Message-ID: <YIv969BCnPgXzrcg@kroah.com> (raw)
In-Reply-To: <20210430124317.97376-1-linux@fw-web.de>

On Fri, Apr 30, 2021 at 02:43:17PM +0200, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
> 
> currently unspecific mediatek.ko is built,
> change this by adding subsystem

I am sorry, I do not understand this changelog text.  What are you doing
here and why?

> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
>  drivers/usb/musb/Makefile                   | 2 +-
>  drivers/usb/musb/{mediatek.c => musb_mtk.c} | 0

Why rename this file, will that not break existing setups that expect
the module to be named this?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Frank Wunderlich <linux@fw-web.de>
Cc: linux-mediatek@lists.infradead.org,
	Frank Wunderlich <frank-w@public-files.de>,
	Bin Liu <b-liu@ti.com>, Matthias Brugger <matthias.bgg@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	David Miller <davem@davemloft.net>,
	DENG Qingfang <dqfext@gmail.com>
Subject: Re: [PATCH] musb: mediatek: rename driver
Date: Fri, 30 Apr 2021 14:54:03 +0200	[thread overview]
Message-ID: <YIv969BCnPgXzrcg@kroah.com> (raw)
In-Reply-To: <20210430124317.97376-1-linux@fw-web.de>

On Fri, Apr 30, 2021 at 02:43:17PM +0200, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
> 
> currently unspecific mediatek.ko is built,
> change this by adding subsystem

I am sorry, I do not understand this changelog text.  What are you doing
here and why?

> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
>  drivers/usb/musb/Makefile                   | 2 +-
>  drivers/usb/musb/{mediatek.c => musb_mtk.c} | 0

Why rename this file, will that not break existing setups that expect
the module to be named this?

thanks,

greg k-h

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Frank Wunderlich <linux@fw-web.de>
Cc: linux-mediatek@lists.infradead.org,
	Frank Wunderlich <frank-w@public-files.de>,
	Bin Liu <b-liu@ti.com>, Matthias Brugger <matthias.bgg@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	David Miller <davem@davemloft.net>,
	DENG Qingfang <dqfext@gmail.com>
Subject: Re: [PATCH] musb: mediatek: rename driver
Date: Fri, 30 Apr 2021 14:54:03 +0200	[thread overview]
Message-ID: <YIv969BCnPgXzrcg@kroah.com> (raw)
In-Reply-To: <20210430124317.97376-1-linux@fw-web.de>

On Fri, Apr 30, 2021 at 02:43:17PM +0200, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
> 
> currently unspecific mediatek.ko is built,
> change this by adding subsystem

I am sorry, I do not understand this changelog text.  What are you doing
here and why?

> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
>  drivers/usb/musb/Makefile                   | 2 +-
>  drivers/usb/musb/{mediatek.c => musb_mtk.c} | 0

Why rename this file, will that not break existing setups that expect
the module to be named this?

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-04-30 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 12:43 [PATCH] musb: mediatek: rename driver Frank Wunderlich
2021-04-30 12:43 ` Frank Wunderlich
2021-04-30 12:43 ` Frank Wunderlich
2021-04-30 12:54 ` Greg Kroah-Hartman [this message]
2021-04-30 12:54   ` Greg Kroah-Hartman
2021-04-30 12:54   ` Greg Kroah-Hartman
2021-04-30 13:30   ` Aw: " Frank Wunderlich
2021-04-30 13:30     ` Frank Wunderlich
2021-04-30 13:30     ` Frank Wunderlich
2021-04-30 13:57     ` Greg Kroah-Hartman
2021-04-30 13:57       ` Greg Kroah-Hartman
2021-04-30 13:57       ` Greg Kroah-Hartman
2021-04-30 14:38       ` Frank Wunderlich
2021-04-30 14:38         ` Frank Wunderlich
2021-04-30 14:38         ` Frank Wunderlich

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=YIv969BCnPgXzrcg@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b-liu@ti.com \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=frank-w@public-files.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@fw-web.de \
    --cc=matthias.bgg@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.