All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Darius Augulis <augulis.darius@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, kgene.kim@samsung.com,
	ben-linux@fluff.org, linux-kernel@vger.kernel.org,
	paulius.zaleckas@gmail.com, linux-serial@vger.kernel.org
Subject: Re: [RESEND PATCH] serial: samsung: fix device name
Date: Fri, 24 Sep 2010 00:40:39 +0100	[thread overview]
Message-ID: <4C9BE577.4050504@fluff.org> (raw)
In-Reply-To: <20100923190212.18863.25678.stgit@darius-desktop>

On 23/09/10 20:15, Darius Augulis wrote:
> Swap device and driver names in serial/samsung.c

This is far too short, please see the notes below on trying
to make this more informative.

> Signed-off-by: Darius Augulis <augulis.darius@gmail.com>
> ---
> 
> This patch was submitted about 3 months ago, but still not merged.
> There was another similar patch from Joonyoung Shim
> <jy0922.shim@samsung.com> and was discussed here:
> http://marc.info/?l=linux-serial&m=127416101222281&w=2.
> Joonyoung Shim acked my patch and other people on ARM mailing list
> acked it. The maintainer, Ben Dooks, still not responding for
> a long time. Another maintainer, Kukjin Kim, refused to merge
> it without Ben's review.
> I would like to ask somebody pick up this bugfix.

I belive last time this was brought up I asked about the affect
this has on the userspace. The following issues would be helpful
or essential to have noted in the header about the effect of this.

- Does it change the /dev name of the device? if so I would thinl
  carefully about applying it, as it would be a change in the way
  that userspace sees the kernel.

- Does it change the kernel output itself? A note on what diffeences
  can be seen in things like dmesg would be helpful.

- Are there any other side effects

- Why is this a bug? Maybe the previous points will explain what is
  going on, but if not, then a reasonably concise description of
  what is going on here.

>  drivers/serial/samsung.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/serial/samsung.c b/drivers/serial/samsung.c
> index b1156ba..25c0d0f 100644
> --- a/drivers/serial/samsung.c
> +++ b/drivers/serial/samsung.c
> @@ -883,10 +883,10 @@ static struct uart_ops s3c24xx_serial_ops = {
>  
>  static struct uart_driver s3c24xx_uart_drv = {
>  	.owner		= THIS_MODULE,
> -	.dev_name	= "s3c2410_serial",
> +	.driver_name    = "s3c2410_serial",
>  	.nr		= CONFIG_SERIAL_SAMSUNG_UARTS,
>  	.cons		= S3C24XX_SERIAL_CONSOLE,
> -	.driver_name	= S3C24XX_SERIAL_NAME,
> +	.dev_name       = S3C24XX_SERIAL_NAME,
>  	.major		= S3C24XX_SERIAL_MAJOR,
>  	.minor		= S3C24XX_SERIAL_MINOR,
>  };
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] serial: samsung: fix device name
Date: Fri, 24 Sep 2010 00:40:39 +0100	[thread overview]
Message-ID: <4C9BE577.4050504@fluff.org> (raw)
In-Reply-To: <20100923190212.18863.25678.stgit@darius-desktop>

On 23/09/10 20:15, Darius Augulis wrote:
> Swap device and driver names in serial/samsung.c

This is far too short, please see the notes below on trying
to make this more informative.

> Signed-off-by: Darius Augulis <augulis.darius@gmail.com>
> ---
> 
> This patch was submitted about 3 months ago, but still not merged.
> There was another similar patch from Joonyoung Shim
> <jy0922.shim@samsung.com> and was discussed here:
> http://marc.info/?l=linux-serial&m=127416101222281&w=2.
> Joonyoung Shim acked my patch and other people on ARM mailing list
> acked it. The maintainer, Ben Dooks, still not responding for
> a long time. Another maintainer, Kukjin Kim, refused to merge
> it without Ben's review.
> I would like to ask somebody pick up this bugfix.

I belive last time this was brought up I asked about the affect
this has on the userspace. The following issues would be helpful
or essential to have noted in the header about the effect of this.

- Does it change the /dev name of the device? if so I would thinl
  carefully about applying it, as it would be a change in the way
  that userspace sees the kernel.

- Does it change the kernel output itself? A note on what diffeences
  can be seen in things like dmesg would be helpful.

- Are there any other side effects

- Why is this a bug? Maybe the previous points will explain what is
  going on, but if not, then a reasonably concise description of
  what is going on here.

>  drivers/serial/samsung.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/serial/samsung.c b/drivers/serial/samsung.c
> index b1156ba..25c0d0f 100644
> --- a/drivers/serial/samsung.c
> +++ b/drivers/serial/samsung.c
> @@ -883,10 +883,10 @@ static struct uart_ops s3c24xx_serial_ops = {
>  
>  static struct uart_driver s3c24xx_uart_drv = {
>  	.owner		= THIS_MODULE,
> -	.dev_name	= "s3c2410_serial",
> +	.driver_name    = "s3c2410_serial",
>  	.nr		= CONFIG_SERIAL_SAMSUNG_UARTS,
>  	.cons		= S3C24XX_SERIAL_CONSOLE,
> -	.driver_name	= S3C24XX_SERIAL_NAME,
> +	.dev_name       = S3C24XX_SERIAL_NAME,
>  	.major		= S3C24XX_SERIAL_MAJOR,
>  	.minor		= S3C24XX_SERIAL_MINOR,
>  };
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2010-09-23 23:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 19:15 [RESEND PATCH] serial: samsung: fix device name Darius Augulis
2010-09-23 19:15 ` Darius Augulis
2010-09-23 19:40 ` Wolfram Sang
2010-09-23 19:40   ` Wolfram Sang
2010-09-23 23:40 ` Ben Dooks [this message]
2010-09-23 23:40   ` Ben Dooks
2010-09-24  6:57   ` Darius Augulis
2010-09-24  6:57     ` Darius Augulis
2010-09-24  6:57     ` Darius Augulis
2010-09-24  7:34     ` Simon Richter
2010-09-24  7:34       ` Simon Richter
2010-09-24  7:34       ` Simon Richter
2010-09-24  7:42       ` Russell King - ARM Linux
2010-09-24  7:42         ` Russell King - ARM Linux
2010-09-27  0:17       ` Ben Dooks
2010-09-27  0:17         ` Ben Dooks
2010-09-24 16:37     ` Paulius Zaleckas
2010-09-24 16:37       ` Paulius Zaleckas
2010-09-24 16:37       ` Paulius Zaleckas
2010-09-27  0:18       ` Ben Dooks
2010-09-27  0:18         ` Ben Dooks
2010-09-27  8:20         ` Paulius Zaleckas
2010-09-27  8:20           ` Paulius Zaleckas
2010-09-27  8:20           ` Paulius Zaleckas
2010-09-27  8:24         ` Darius Augulis
2010-09-27  8:24           ` Darius Augulis
2010-09-27  8:24           ` Darius Augulis
2011-01-12  6:15           ` Kukjin Kim
2011-01-12  6:15             ` Kukjin Kim
2011-01-12  6:15             ` Kukjin Kim
2010-10-22  7:02         ` Darius Augulis
2010-10-22  7:02           ` Darius Augulis
2010-10-22  7:02           ` Darius Augulis

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=4C9BE577.4050504@fluff.org \
    --to=ben-linux@fluff.org \
    --cc=augulis.darius@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=paulius.zaleckas@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.