From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cmroliv@gmail.com, marcel@holtmann.org, pali.rohar@gmail.com,
kernel list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: patch "staging: remove nokia_hp4p driver
Date: Sun, 31 Aug 2014 00:44:30 +0200 [thread overview]
Message-ID: <20140830224430.GA19622@amd> (raw)
In-Reply-To: <20140830220417.GA15000@kroah.com>
Hi!
> >
> > What is going on here? I get flamed for not cleaning up the driver,
> > because I cleaned it up before merging to -staging. Ok, so I did more
> > cleanups, sent 3 cleanup patches, no reaction on those, and now I got
> > a note that you are going to remove the driver...?
>
> For the 3 "cleanup" patches, the first one was rejected and you said to
> not include it, so I couldn't apply the others.
That was different series. I'm talking about:
[PATCH 1/3] staging: nokia_h4: switch to right types and use bdaddr_t
[PATCH 2/3] staging: nokia_h4: avoid __uX types
[PATCH 3/3] staging: use inlines where it makes sense
That is still valid and received no comments at all.
> > Please don't, I'd still like to clean the driver up and get included,
> > as n900's are still under active use.
>
> As the Bluetooth maintainer has said a number of times, he doesn't want
> the driver in the tree as it is not doing the correct things. It's been
> a long time in the tree with no work on it at all, and I follow the
> suggestions of the maintainers of the subsystems that staging drivers
> follow.
You asked for more work and explained how easy it is to revert the
removal.
I did more work, you ignored it, and are removing the driver, anyway.
> I suggest cleaning this up in your own tree, and then just submitting it
> for inclusion in the "normal" part of the kernel. That way I'm not
...creating a mess in the history, and fun merge problems for
people actually using the driver :-(. And yes, n900 people actually
are using it and have their own changes on top of it.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-08-30 22:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14094295422869@kroah.com>
2014-08-30 21:30 ` patch "staging: remove nokia_hp4p driver Pavel Machek
2014-08-30 22:04 ` Greg KH
2014-08-30 22:44 ` Pavel Machek [this message]
2014-08-30 22:49 ` Greg KH
2014-08-31 9:28 ` Pavel Machek
2014-08-30 23:09 ` Marcel Holtmann
2014-08-31 8:23 ` Pali Rohár
2014-08-31 9:51 ` Pavel Machek
2014-09-01 22:16 ` Marcel Holtmann
2014-09-04 11:36 ` Pavel Machek
2014-12-03 12:33 ` Pavel Machek
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=20140830224430.GA19622@amd \
--to=pavel@ucw.cz \
--cc=cmroliv@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pali.rohar@gmail.com \
--cc=torvalds@linux-foundation.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