linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: serial: samsung: rename to fix build warning
Date: Mon, 11 Nov 2019 15:18:38 +0000	[thread overview]
Message-ID: <CADVatmMzZ9AByeUBtqdrfE_apK58oMYLxSuBrDdLh2XTQzKE9A@mail.gmail.com> (raw)
In-Reply-To: <20191104164351.GA2269025@kroah.com>

Hi Greg,

On Mon, Nov 4, 2019 at 4:43 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Fri, Oct 18, 2019 at 08:47:07PM +0100, Sudip Mukherjee wrote:
> > The build of arm allmodconfig gives a warning:
> >
> > warning: same module names found:
> >   drivers/tty/serial/samsung.ko
> >   drivers/mtd/nand/onenand/samsung.ko
> >
> > Rename drivers/tty/serial/samsung.c to drivers/tty/serial/samsung_tty.c
> > to fix the warning.
> >
<snip>
>
>
> What are you going to break if you rename this module?

hopefully nothing.

>
> What configs enable both of these other than allmodconfig?  Why rename
> the tty driver and not the mtd driver?  Why not both?

But, there is no other config defined which has both enabled. Though I can
make one, but since it is not defined and no one else has reported this, I think
its better if you discard this. ( I think you already have :) )  or if
you want I can
send a v2 renaming both.


-- 
Regards
Sudip

  reply	other threads:[~2019-11-11 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 19:47 [PATCH] tty: serial: samsung: rename to fix build warning Sudip Mukherjee
2019-11-04 16:43 ` Greg Kroah-Hartman
2019-11-11 15:18   ` Sudip Mukherjee [this message]
2019-11-14  3:47     ` Greg Kroah-Hartman

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=CADVatmMzZ9AByeUBtqdrfE_apK58oMYLxSuBrDdLh2XTQzKE9A@mail.gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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).