From: Arvind Sankar <nivedita@alum.mit.edu>
To: Arvind Sankar <nivedita@alum.mit.edu>
Cc: "David S . Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc/console: kill off obsolete declarations
Date: Fri, 3 Jan 2020 12:17:35 -0500 [thread overview]
Message-ID: <20200103171735.GB1308999@rani.riverdale.lan> (raw)
In-Reply-To: <20191216221004.3476562-1-nivedita@alum.mit.edu>
On Mon, Dec 16, 2019 at 05:10:04PM -0500, Arvind Sankar wrote:
> commit 09d3f3f0e02c ("sparc: Kill PROM console driver.") missed removing
> the declarations of the deleted prom_con structure and prom_con_init
> function from console.h. Kill them off now.
>
Hi David, happy new year!
Reminder for the following small cleanup patch.
https://lore.kernel.org/lkml/20191216221004.3476562-1-nivedita@alum.mit.edu/
prev parent reply other threads:[~2020-01-03 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 22:10 [PATCH] sparc/console: kill off obsolete declarations Arvind Sankar
2020-01-03 17:17 ` Arvind Sankar [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=20200103171735.GB1308999@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).