From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Maarten ter Huurne <maarten@treewalker.org>,
linux-usb@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Paul Cercueil <paul@crapouillou.net>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] USB: ohci-jz4740: Remove obsolete driver
Date: Fri, 13 May 2016 18:50:23 +0200 [thread overview]
Message-ID: <20160513165023.GA31809@kroah.com> (raw)
In-Reply-To: <20160513164017.GL4215@linux-mips.org>
On Fri, May 13, 2016 at 06:40:17PM +0200, Ralf Baechle wrote:
> Maarten,
>
> if you submit a USB change to the USB mailing list and maintainer the
> probability for the maintainer to ack this patch will actuall rise
> significantly ;-)
>
> Greg, I assume this patch is ok to merge or do you want to funnel it
> hrough your tree? I think it would be good to take this through the
> MIPS tree together with the remainder of the series.
Deleting code? Yes, I'm all for that :)
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
And yes, actually letting the maintainers know is a good thing, unless
you don't want your patches applied...
thanks,
greg k-h
next prev parent reply other threads:[~2016-05-13 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 18:58 [PATCH 1/3] MIPS: JZ4740: Qi LB60: Remove support for AVT2 variant Maarten ter Huurne
2016-04-18 18:58 ` [PATCH 2/3] MIPS: JZ4740: Probe OHCI platform device via DT Maarten ter Huurne
2016-04-18 18:58 ` [PATCH 3/3] USB: ohci-jz4740: Remove obsolete driver Maarten ter Huurne
2016-05-13 16:40 ` Ralf Baechle
2016-05-13 16:50 ` Greg Kroah-Hartman [this message]
2016-04-23 11:57 ` [PATCH 1/3] MIPS: JZ4740: Qi LB60: Remove support for AVT2 variant Lars-Peter Clausen
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=20160513165023.GA31809@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=maarten@treewalker.org \
--cc=paul@crapouillou.net \
--cc=ralf@linux-mips.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).