All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: davem@davemloft.net, samuel@sortiz.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 4/4] staging: irda: add a TODO file.
Date: Sun, 27 Aug 2017 17:03:34 +0200	[thread overview]
Message-ID: <20170827150334.32495-5-gregkh@linuxfoundation.org> (raw)
In-Reply-To: <20170827150334.32495-1-gregkh@linuxfoundation.org>

The irda code will be deleted in a future kernel release, so no need to
have anyone do any new work on it.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 drivers/staging/irda/TODO | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 drivers/staging/irda/TODO

diff --git a/drivers/staging/irda/TODO b/drivers/staging/irda/TODO
new file mode 100644
index 000000000000..7d98a5cffaff
--- /dev/null
+++ b/drivers/staging/irda/TODO
@@ -0,0 +1,4 @@
+The irda code will be removed soon from the kernel tree as it is old and
+obsolete and broken.
+
+Don't worry about fixing up anything here, it's not needed.
-- 
2.14.1

  parent reply	other threads:[~2017-08-27 15:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27 15:03 [PATCH 0/4] irda: move it to drivers/staging so we can delete it Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 1/4] irda: move net/irda/ to drivers/staging/irda/net/ Greg Kroah-Hartman
2017-08-27 15:03   ` Greg Kroah-Hartman
2017-08-30  6:04   ` [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel kernel test robot
2017-08-30  6:04     ` kernel test robot
2017-08-30  6:12     ` Greg Kroah-Hartman
2017-08-30  6:12       ` Greg Kroah-Hartman
2017-08-30  6:19       ` Ye Xiaolong
2017-08-30  6:19         ` Ye Xiaolong
2017-08-27 15:03 ` [PATCH 2/4] irda: move drivers/net/irda to drivers/staging/irda/drivers Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 3/4] irda: move include/net/irda into staging subdirectory Greg Kroah-Hartman
2017-08-27 15:03 ` Greg Kroah-Hartman [this message]
2017-08-27 15:35 ` [PATCH 0/4] irda: move it to drivers/staging so we can delete it Joe Perches
2017-08-27 16:13   ` Greg Kroah-Hartman
2017-08-27 16:13     ` Greg Kroah-Hartman
2017-08-27 16:19     ` Joe Perches
2017-08-27 16:19       ` Joe Perches
2017-08-27 16:53       ` Greg Kroah-Hartman
2017-08-27 16:53         ` Greg Kroah-Hartman
2017-08-27 23:15         ` Joe Perches
2017-08-28 23:42 ` David Miller
2017-08-28 23:42   ` David Miller
2017-08-28 23:46   ` Joe Perches
2017-08-29  5:06     ` Greg KH
2017-08-29  5:06       ` Greg KH
2017-08-29 21:32   ` Ondrej Zary
2017-08-31  4:30     ` Greg KH
2017-08-31  4:30       ` Greg KH
2017-08-31  7:31       ` Ondrej Zary
2017-08-31  7:31         ` Ondrej Zary
2017-08-29 10:59 ` Geert Uytterhoeven
2017-08-29 11:11   ` Stefano Brivio
2017-08-29 11:11     ` Stefano Brivio
2017-08-29 11:28     ` Greg Kroah-Hartman
2017-08-29 12:11       ` Geert Uytterhoeven
2017-08-29 14:48         ` Greg Kroah-Hartman
2017-08-29 16:49           ` David Miller
2017-08-29 16:49             ` David Miller
2017-08-29 16:38   ` David Miller

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=20170827150334.32495-5-gregkh@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=samuel@sortiz.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 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.