From: Greg KH <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [char-misc-next 11/11] mei: revamp mei bus code
Date: Mon, 25 May 2015 09:20:58 -0700 [thread overview]
Message-ID: <20150525162058.GE9772@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B3C4A0C0A@hasmsx109.ger.corp.intel.com>
On Mon, May 25, 2015 at 04:40:50AM +0000, Winkler, Tomas wrote:
>
> > > > This is a lot to do in just one patch. Any chance you can split it up
> > > > into reviewable pieces?
> > >
> > > I thought it would be harder to swallow but I'm not sure how to really
> > > split this into working pieces w/o do some artificial steps which
> > > I will have to validate again to keep the code bisectable.
> >
> > That's fine, that's your job to do :)
>
> I'd would prefer to do something that wasn't' already done.
Huh? Your job is to split changes up into tiny logical pieces that are
easy to review. That isn't "done" here.
> > > What could be naturally factored out is already in separate patches in this
> > series.
> > > The patch is maybe bigger because of code moves between files but what has
> > really changes is just bus.c
> >
> > Then do the movement of functions around in one patch, and then the
> > logical changes in others. Come on, you know how this whole thing
> > works, don't be lazy here...
> >
> Yep, I know how it works, but here it just didn't fit as the logical changes moved also the code.
> Okay, I will split the code but allow me one comment, I think that you were lazy too go into details and you didn't send us to hell when we first submitted that bus code.
So because I wasn't hard enough on your initial reviews of this code,
you are now blaming me for this needed rework?
I seem to recall that I gave a lot of feedback on those original
patches, but if you want me to be harder and take a much closer look at
all of your patches, I'll be glad to do so. Be aware, that this is
going to slow down the acceptance rates of your patches, and I am going
to now be _very_ pedantic and grumpy.
Remember, you asked for it, this is going to be fun, for me, not you...
greg k-h
prev parent reply other threads:[~2015-05-25 16:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 12:53 [char-misc-next 01/11] mei: consume flow control on the first chunk of writing Tomas Winkler
2015-05-07 12:53 ` [char-misc-next 02/11] mei: request autosuspend at the end of write Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 03/11] mei: add also write waiting list to runtime pm blockers Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 04/11] uuid: extract macros for assigning raw arrays Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 05/11] mei: bus: report also uuid in module alias Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 06/11] mei: bus: add name and uuid into device attributes Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 07/11] NFC: mei_phy: move all nfc logic from mei driver to nfc Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 08/11] mei: bus: kill mei_cl_ops Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 09/11] NFC: mei_phy: adjust mei nfc header according the spec Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 10/11] mei: export mei client device struct to external use Tomas Winkler
2015-05-07 12:54 ` [char-misc-next 11/11] mei: revamp mei bus code Tomas Winkler
2015-05-24 18:19 ` Greg KH
2015-05-24 21:29 ` Winkler, Tomas
2015-05-25 1:46 ` Greg KH
2015-05-25 4:40 ` Winkler, Tomas
2015-05-25 16:20 ` Greg KH [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=20150525162058.GE9772@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=tomas.winkler@intel.com \
/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