All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	Samuel Iglesias Gonsalvez <siglesias@igalia.com>,
	Jens Taprogge <jens.taprogge@taprogge.org>,
	Jiri Slaby <jslaby@suse.com>,
	linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 0/3] tty: drop unused iflag macro
Date: Thu, 23 May 2019 11:21:27 +0200	[thread overview]
Message-ID: <20190523092127.GD568@localhost> (raw)
In-Reply-To: <20190426055925.13430-1-johan@kernel.org>

On Fri, Apr 26, 2019 at 07:59:22AM +0200, Johan Hovold wrote:
> I noticed that the RELEVANT_IFLAG() macro was unused in USB serial and
> turns out there were a few more instances that could be dropped.
> 
> I have some pending changes that may conflict with the corresponding
> change to USB serial so I'll take that one separately through my tree,
> but perhaps the rest could go through Greg's tty tree.

> Johan Hovold (3):
>   tty: simserial: drop unused iflag macro
>   tty: ipoctal: drop unused iflag macro
>   tty: cpm_uart: drop unused iflag macro
> 
>  arch/ia64/hp/sim/simserial.c                | 2 --
>  drivers/ipack/devices/ipoctal.h             | 1 -
>  drivers/tty/serial/cpm_uart/cpm_uart_core.c | 2 --
>  3 files changed, 5 deletions(-)

Greg, do you still have these clean-ups in your queue? Want me to resend
with Tony's ack?

Johan

  parent reply	other threads:[~2019-05-23  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  5:59 [PATCH 0/3] tty: drop unused iflag macro Johan Hovold
2019-04-26  5:59 ` [PATCH 1/3] tty: simserial: " Johan Hovold
2019-04-26 16:29   ` Luck, Tony
2019-04-26  5:59 ` [PATCH 2/3] tty: ipoctal: " Johan Hovold
2019-04-26  5:59 ` [PATCH 3/3] tty: cpm_uart: " Johan Hovold
2019-05-23  9:21 ` Johan Hovold [this message]
2019-05-23  9:31   ` [PATCH 0/3] tty: " Greg Kroah-Hartman
2019-05-23 10:39     ` Johan Hovold

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=20190523092127.GD568@localhost \
    --to=johan@kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jens.taprogge@taprogge.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siglesias@igalia.com \
    --cc=tony.luck@intel.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.