From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH] staging: evict abandoned 68360serial.c driver from 3.4
Date: Wed, 28 Mar 2012 13:02:29 -0400 [thread overview]
Message-ID: <4F734425.9010204@windriver.com> (raw)
In-Reply-To: <20120328150528.GD19862@kroah.com>
On 12-03-28 11:05 AM, Greg KH wrote:
> On Tue, Mar 27, 2012 at 07:07:11PM -0400, Paul Gortmaker wrote:
>> commit 3a0db7215c88077b61a673215756ec4a0dc0c7a5
>>
>> "TTY: serial, move 68360 driver to staging"
>>
>> did so because the driver had remained broken since 2008. It also
>> added this text to the TODO file:
>>
>> "If no one steps up to adopt any of these drivers, they will
>> be removed in the 3.4 release."
>>
>> A quick search on the internet doesn't reveal anyone actively
>> trying to update/fix this driver, so follow through on the above
>> and remove it from the pending 3.4 release.
>>
>> Cc: Jiri Slaby <jslaby@suse.cz>
>> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
>> Cc: Alan Cox <alan@linux.intel.com>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> Thanks for this, but as I missed the merge window for 3.4, I'll queue it
> up for 3.5 just to be safe.
Thanks Greg,
I only happened to stumble upon it last night or I would have
sent it earlier. No harm in it sitting there another release.
Feel free to prune the "from 3.4" off the end of the shortlog.
Paul.
>
> greg k-h
prev parent reply other threads:[~2012-03-28 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 23:07 [PATCH] staging: evict abandoned 68360serial.c driver from 3.4 Paul Gortmaker
2012-03-28 7:31 ` Geert Uytterhoeven
2012-03-28 15:05 ` Greg KH
2012-03-28 17:02 ` Paul Gortmaker [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=4F734425.9010204@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=alan@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-serial@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 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.