From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>,
richard@nod.at, johannes@sipsolutions.net
Cc: linux-um@lists.infradead.org
Subject: Re: [PATCH] um: remove unused reactivate_chan() declaration
Date: Wed, 14 Sep 2022 09:38:31 +0100 [thread overview]
Message-ID: <b203541c-680e-7ec8-b718-fed01911dee0@cambridgegreys.com> (raw)
In-Reply-To: <20220914073027.1340509-1-cuigaosheng1@huawei.com>
On 14/09/2022 08:30, Gaosheng Cui wrote:
> All uses of reactivate_chan() were removed by
> commit 940b241d9050 ("um: Remove obsolete reenable_XX
> calls"), so remove the declaration, too.
>
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
> arch/um/drivers/chan.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/um/drivers/chan.h b/arch/um/drivers/chan.h
> index c37cc4f26f91..3fec3b8406e9 100644
> --- a/arch/um/drivers/chan.h
> +++ b/arch/um/drivers/chan.h
> @@ -36,7 +36,6 @@ extern int console_write_chan(struct chan *chan, const char *buf,
> int len);
> extern int console_open_chan(struct line *line, struct console *co);
> extern void deactivate_chan(struct chan *chan, int irq);
> -extern void reactivate_chan(struct chan *chan, int irq);
> extern void chan_enable_winch(struct chan *chan, struct tty_port *port);
> extern int enable_chan(struct line *line);
> extern void close_chan(struct line *line);
Acked-By: Anton Ivanov <anton.ivanov@cambridgegreys.com>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2022-09-14 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 7:30 [PATCH] um: remove unused reactivate_chan() declaration Gaosheng Cui
2022-09-14 8:38 ` Anton Ivanov [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=b203541c-680e-7ec8-b718-fed01911dee0@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=cuigaosheng1@huawei.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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).