All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org,
	tj@kernel.org, akpm@linux-foundation.org,
	linux-pm@vger.kernel.org, jiangshanlai@gmail.com,
	rafael@kernel.org, len.brown@intel.com, zwisler@kernel.org,
	dan.j.williams@intel.com, dave.jiang@intel.com,
	bvanassche@acm.org
Subject: Re: [driver-core PATCH v6 2/9] async: Add support for queueing on specific NUMA node
Date: Tue, 13 Nov 2018 23:10:14 +0100	[thread overview]
Message-ID: <20181113221014.GB2235@amd> (raw)
In-Reply-To: <20181111203304.GA16871@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]

Hi!

> > > > Signed-off-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
> > > > ---
> > > 
> > > No one else from Intel has reviewed/verified this code at all?
> > > 
> > > Please take advantages of the resources you have that most people do
> > > not, get reviewes from your coworkers please before you send this out
> > > again, as they can give you valuable help before the community has to
> > > review the code...
> > 
> > We always said to companies we want to see code as soon as
> > possible. You don't have to review their code, but discouraging the
> > posting seems wrong.
> 
> I have a long history of Intel using me for their basic "find the
> obvious bugs" review process for new driver subsystems and core changes.
> When I see new major patches show up from an Intel developer without
> _any_ other review from anyone else, directed at me, I get suspicious it
> is happening again.
> 
> If you note, Intel is the _only_ company I say this to their developers
> because of this problem combined with the fact that they have a whole
> load of developers that they should be running things by first.
> 
> And yes, to answer Dan's point, we do want to do review in public.  But
> this is v6 of a core patchset and there has been NO review from anyone
> else at Intel on this.  So if that review was going to happen, one would
> have thought it would have by now, instead of relying on me to do it.
> 
> And yes, I am grumpy, but I am grumpy because of the history here.  I am
> not trying to discourage anything, only to take ADVANTAGE of resources
> that almost no other company provides.
> 
> Hope this helps explain my statement here.

Thanks for explanation. I did not have same bad experience with Intel,
so I did not understand what was going on.

Best regards,

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-11-13 22:10 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 18:06 [driver-core PATCH v6 0/9] Add NUMA aware async_schedule calls Alexander Duyck
2018-11-08 18:06 ` Alexander Duyck
2018-11-08 18:06 ` [driver-core PATCH v6 1/9] workqueue: Provide queue_work_node to queue work near a given NUMA node Alexander Duyck
2018-11-08 18:06   ` Alexander Duyck
2018-11-27  1:01   ` Dan Williams
2018-11-27  1:01     ` Dan Williams
2018-11-08 18:06 ` [driver-core PATCH v6 2/9] async: Add support for queueing on specific " Alexander Duyck
2018-11-08 18:06   ` Alexander Duyck
2018-11-08 23:36   ` Bart Van Assche
2018-11-08 23:36     ` Bart Van Assche
2018-11-08 23:36     ` Bart Van Assche
2018-11-11 19:32   ` Greg KH
2018-11-11 19:32     ` Greg KH
2018-11-11 19:32     ` Greg KH
2018-11-11 19:53     ` Dan Williams
2018-11-11 19:53       ` Dan Williams
2018-11-11 19:53       ` Dan Williams
2018-11-11 20:35       ` Greg KH
2018-11-11 20:35         ` Greg KH
2018-11-11 20:35         ` Greg KH
2018-11-11 22:17         ` Dan Williams
2018-11-11 22:17           ` Dan Williams
2018-11-11 22:17           ` Dan Williams
2018-11-11 23:27         ` Alexander Duyck
2018-11-11 23:27           ` Alexander Duyck
2018-11-11 23:27           ` Alexander Duyck
2018-11-11 19:59     ` Pavel Machek
2018-11-11 20:33       ` Greg KH
2018-11-11 20:33         ` Greg KH
2018-11-11 21:24         ` Bart Van Assche
2018-11-11 21:24           ` Bart Van Assche
2018-11-13 22:10         ` Pavel Machek [this message]
2018-11-27  1:10   ` Dan Williams
2018-11-27  1:10     ` Dan Williams
2018-11-27  1:10     ` Dan Williams
2018-11-08 18:06 ` [driver-core PATCH v6 3/9] device core: Consolidate locking and unlocking of parent and device Alexander Duyck
2018-11-08 18:06   ` Alexander Duyck
2018-11-08 18:06   ` Alexander Duyck
2018-11-08 22:43   ` jane.chu
2018-11-08 22:43     ` jane.chu-QHcLZuEGTsvQT0dZR+AlfA
2018-11-08 22:43     ` jane.chu
2018-11-08 22:48     ` Alexander Duyck
2018-11-08 22:48       ` Alexander Duyck
2018-11-27  1:44   ` Dan Williams
2018-11-27  1:44     ` Dan Williams
2018-11-08 18:07 ` [driver-core PATCH v6 4/9] driver core: Move async_synchronize_full call Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-27  2:11   ` Dan Williams
2018-11-27  2:11     ` Dan Williams
2018-11-27 17:38     ` Alexander Duyck
2018-11-27 17:38       ` Alexander Duyck
2018-11-27 20:35       ` Dan Williams
2018-11-27 20:35         ` Dan Williams
2018-11-27 21:36         ` Alexander Duyck
2018-11-27 21:36           ` Alexander Duyck
2018-11-27 22:26           ` Dan Williams
2018-11-27 22:26             ` Dan Williams
2018-11-27 22:26             ` Dan Williams
2018-11-08 18:07 ` [driver-core PATCH v6 5/9] driver core: Establish clear order of operations for deferred probe and remove Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-08 23:47   ` Bart Van Assche
2018-11-08 23:47     ` Bart Van Assche
2018-11-08 23:47     ` Bart Van Assche
2018-11-08 18:07 ` [driver-core PATCH v6 6/9] driver core: Probe devices asynchronously instead of the driver Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-08 23:59   ` Bart Van Assche
2018-11-08 23:59     ` Bart Van Assche
2018-11-27  2:48   ` Dan Williams
2018-11-27  2:48     ` Dan Williams
2018-11-27  2:48     ` Dan Williams
2018-11-27 17:57     ` Alexander Duyck
2018-11-27 17:57       ` Alexander Duyck
2018-11-27 18:32       ` Dan Williams
2018-11-27 18:32         ` Dan Williams
2018-11-08 18:07 ` [driver-core PATCH v6 7/9] driver core: Attach devices on CPU local to device node Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-27  4:50   ` Dan Williams
2018-11-27  4:50     ` Dan Williams
2018-11-27  4:50     ` Dan Williams
2018-11-08 18:07 ` [driver-core PATCH v6 8/9] PM core: Use new async_schedule_dev command Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-27  4:52   ` Dan Williams
2018-11-27  4:52     ` Dan Williams
2018-11-27  4:52     ` Dan Williams
2018-11-08 18:07 ` [driver-core PATCH v6 9/9] libnvdimm: Schedule device registration on node local to the device Alexander Duyck
2018-11-08 18:07   ` Alexander Duyck
2018-11-27  2:21   ` Dan Williams
2018-11-27  2:21     ` Dan Williams
2018-11-27  2:21     ` Dan Williams
2018-11-27 18:04     ` Alexander Duyck
2018-11-27 19:34       ` Dan Williams
2018-11-27 19:34         ` Dan Williams
2018-11-27 20:33         ` Bart Van Assche
2018-11-27 20:33           ` Bart Van Assche
2018-11-27 20:33           ` Bart Van Assche
2018-11-27 20:50           ` Dan Williams
2018-11-27 20:50             ` Dan Williams
2018-11-27 20:50             ` Dan Williams
2018-11-27 21:22             ` Bart Van Assche
2018-11-27 21:22               ` Bart Van Assche
2018-11-27 21:22               ` Bart Van Assche
2018-11-27 22:34               ` Dan Williams
2018-11-27 22:34                 ` Dan Williams
2018-11-27 22:34                 ` Dan Williams

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=20181113221014.GB2235@amd \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=bvanassche@acm.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiangshanlai@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=tj@kernel.org \
    --cc=zwisler@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.