cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Pavel Machek <pavel@denx.de>
Cc: Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [cip-dev] [PATCH 4.4.y-cip 0/4] serial mctrl_gpio/sh-sci Fixes
Date: Fri, 4 Sep 2020 06:51:48 +0000	[thread overview]
Message-ID: <OSBPR01MB50489D99A0B1C42AEBAD5102AA2D0@OSBPR01MB5048.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <16314C4E8BAB0A6F.8972@lists.cip-project.org>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

Hi Pavel/ Nobuhiro,

> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Lad Prabhakar via lists.cip-project.org
> Sent: 03 September 2020 15:27
> To: cip-dev@lists.cip-project.org; Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>; Pavel Machek <pavel@denx.de>
> Cc: Biju Das <biju.das.jz@bp.renesas.com>
> Subject: [cip-dev] [PATCH 4.4.y-cip 0/4] serial mctrl_gpio/sh-sci Fixes
>
> Hi All,
>
> This patch series adds minor fixes to sh-sci and serial_mctrl_gpio driver.
> All patches in this series are cherry-picked from mainline.
>
> Cheers,
> Prabhakar
>
>
> Frieder Schrempf (1):
>   serial: sh-sci: Don't check for mctrl_gpio_init() returning -ENOSYS
>
> Geert Uytterhoeven (2):
>   serial: sh-sci: Terminate TX DMA during buffer flushing
>   serial: sh-sci: Don't check for mctrl_gpio_to_gpiod() returning error
>
> Stefan Roese (1):
>   serial: mctrl_gpio: Check if GPIO property exisits before requesting
>     it
>
>  drivers/tty/serial/serial_mctrl_gpio.c | 15 +++++++++++++++
>  drivers/tty/serial/sh-sci.c            | 25 +++++++++++++++----------
>  2 files changed, 30 insertions(+), 10 deletions(-)
>
Please ignore this patch series. Pavel has reviewed it and has pointed out the issues. Ill revisit the Terminate TX DMA patch at later point.

Cheers,
Prabhakar


Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany, Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5413): https://lists.cip-project.org/g/cip-dev/message/5413
Mute This Topic: https://lists.cip-project.org/mt/76607960/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

       reply	other threads:[~2020-09-04  6:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16314C4E8BAB0A6F.8972@lists.cip-project.org>
2020-09-04  6:51 ` Lad Prabhakar [this message]
2020-09-03 14:27 [cip-dev] [PATCH 4.4.y-cip 0/4] serial mctrl_gpio/sh-sci Fixes Lad Prabhakar

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=OSBPR01MB50489D99A0B1C42AEBAD5102AA2D0@OSBPR01MB5048.jpnprd01.prod.outlook.com \
    --to=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    /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).