linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Akash Asthana <akashast@codeaurora.org>, gregkh@linuxfoundation.org
Cc: mgautam@codeaurora.org, linux-arm-msm@vger.kernel.org,
	linux-serial@vger.kernel.org,
	Akash Asthana <akashast@codeaurora.org>
Subject: Re: [PATCH v6 0/5] Add wakeup support and move loopback to TIOCM_LOOP
Date: Fri, 22 Nov 2019 10:23:44 -0800	[thread overview]
Message-ID: <5dd827b1.1c69fb81.a7ff0.5ab4@mx.google.com> (raw)
In-Reply-To: <0101016e937a0ef9-36754afa-105c-416f-b308-b5bed0cc0ccb-000000@us-west-2.amazonses.com>

Quoting Akash Asthana (2019-11-22 06:18:00)
> This series adds wakeup support over UART RX line and moves loopback
> support to TIOCM_LOOP.
> Patch 1 & 2 reverts the V2 changes for wakeup support on tty-next tip.
> Patch 3 & 4 adds V6 changes for wakeup support.
> 
> Akash Asthana (5):
>   Revert "tty: serial: qcom_geni_serial: Wakeup over UART RX"
>   Revert "tty: serial: qcom_geni_serial: IRQ cleanup"
>   tty: serial: qcom_geni_serial: IRQ cleanup
>   tty: serial: qcom_geni_serial: Wakeup over UART RX
>   tty: serial: qcom_geni_serial: Move loopback support to TIOCM_LOOP

Maybe the reverts aren't necessary? Is it possible to fix up the patches
that are already merged in Greg's tree?


       reply	other threads:[~2019-11-22 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0101016e937a0ef9-36754afa-105c-416f-b308-b5bed0cc0ccb-000000@us-west-2.amazonses.com>
2019-11-22 18:23 ` Stephen Boyd [this message]
2019-11-25 12:03   ` [PATCH v6 0/5] Add wakeup support and move loopback to TIOCM_LOOP Akash Asthana
2019-11-22 14:17 Akash Asthana

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=5dd827b1.1c69fb81.a7ff0.5ab4@mx.google.com \
    --to=swboyd@chromium.org \
    --cc=akashast@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mgautam@codeaurora.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).