mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Moese <mmoese@suse.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Andreas Geissler <andreas.geissler@men.de>,
	Ben Turner <ben.turner@21net.com>
Subject: Re: [PATCH] 8250-men-mcb: add support for 16z025 and 16z057
Date: Wed, 28 Feb 2018 08:56:33 +0100	[thread overview]
Message-ID: <20180228075633.zkqhiitxaeb5xlmi@linux.suse.de> (raw)
In-Reply-To: <CAHp75VddLV3Ke8J3hYw0wLO_77H8K20J_g=QeLG8B0XYt90ZRA@mail.gmail.com>

Hi,
Thanks for your comments. Let me briefly respond.

On Tue, Feb 27, 2018 at 07:57:34PM +0200, Andy Shevchenko wrote:
> On Tue, Feb 27, 2018 at 5:31 PM, Michael Moese <mmoese@suse.de> wrote:
> > -       else if  (strncmp(mdev->bus->name, "F216", 4) == 0)
> > +       else if (strncmp(mdev->bus->name, "F216", 4) == 0)
> 
> What's changed?
There were two spaces after that if.

> > +       switch (mdev->id) {
> > +       case MEN_UART_ID_Z125:
> > +               num_ports = 1U;
> > +               break;
> > +       case MEN_UART_ID_Z025:
> > +               num_ports = readb(membase) >> 4;
> > +               break;
> > +       case MEN_UART_ID_Z057:
> > +               num_ports = 4U;
> > +               break;
> > +       default:
> > +               dev_err(&mdev->dev, "no supported device!\n");
> > +               return -ENODEV;
> > +       }
> 
> (1)
> 
> > +               data[i].uart.port.mapbase = (unsigned long) mem->start
> > +                                           + (i * MEN_UART_MEM_SIZE);
> 
> Redundant parens.
Well, let me remove them. Gonna do a v2 anyway.

> 
> > +       switch (mdev->id) {
> > +       case MEN_UART_ID_Z125:
> > +               num_ports = 1U;
> > +               break;
> > +       case MEN_UART_ID_Z025:
> > +               num_ports = readb(data[0].uart.port.membase) >> 4;
> > +               break;
> > +       case MEN_UART_ID_Z057:
> > +               num_ports = 4U;
> > +               break;
> > +       default:
> > +               dev_err(&mdev->dev, "no supported device!\n");
> > +               return;
> > +       }
> 
> Can you deduplicate this with (1)?
Well, that sounds like a good idea. Will do this.

> -- 
> With Best Regards,
> Andy Shevchenko

Thanks,
Michael
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

      reply	other threads:[~2018-02-28  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 15:31 Michael Moese
2018-02-27 17:57 ` Andy Shevchenko
2018-02-28  7:56   ` Michael Moese [this message]

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=20180228075633.zkqhiitxaeb5xlmi@linux.suse.de \
    --to=mmoese@suse.de \
    --cc=andreas.geissler@men.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=ben.turner@21net.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jthumshirn@suse.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®