public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	Paul J Murphy <paul.j.murphy@intel.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/1] soc: keembay: Add Keem Bay IMR driver
Date: Fri, 1 May 2020 13:59:29 +0200	[thread overview]
Message-ID: <20200501115929.GA1609634@kroah.com> (raw)
In-Reply-To: <f60aece195cd0700728fc38b0398949a82b72fc3.camel@linux.intel.com>

On Fri, May 01, 2020 at 12:50:36PM +0100, Daniele Alessandrelli wrote:
> Thanks for your feedback.
> 
> > 
> > First off, there is a "proper" way to send patches to the kernel
> > community that Intel has that I do not think you are
> > following.  Please
> > work with the Intel "Linux group" to do that first, as odds are they
> > would have caught all of these issues beforehand (hint, which is why
> > that process is in place...)
> > 
> 
> I actually followed that process and got the OK to try to upstream.

Then someone seriously steered you wrong as I know of one specific thing
you did incorrectly (hint, you needed to get them to sign off on the
patch...)

> I think the issues you identified went uncaught mainly due to the
> limited Linux ARM expertise within that group (and Intel in general).

No, they should know better, if not, there are bigger problems there :(

greg k-h

  reply	other threads:[~2020-05-01 11:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 16:36 [PATCH 0/1] Add IMR driver for Keem Bay Daniele Alessandrelli
2020-04-21 16:36 ` [PATCH 1/1] soc: keembay: Add Keem Bay IMR driver Daniele Alessandrelli
2020-05-01  8:10   ` Greg Kroah-Hartman
2020-05-01 11:50     ` Daniele Alessandrelli
2020-05-01 11:59       ` Greg Kroah-Hartman [this message]
2020-05-24 21:28       ` Pavel Machek
2020-05-25  8:18         ` Arnd Bergmann
2020-05-27 13:31           ` Alessandrelli, Daniele
2020-05-27 14:33             ` Arnd Bergmann
2020-05-27 17:43               ` Daniele Alessandrelli
2020-05-27 18:59                 ` Arnd Bergmann
2020-05-28 12:27                   ` Daniele Alessandrelli
2020-05-28 11:22             ` Pavel Machek
2020-05-28 13:00               ` Daniele Alessandrelli
2020-05-07 17:44   ` Pavel Machek
2020-04-30 19:49 ` [PATCH 0/1] Add IMR driver for Keem Bay Alessandrelli, Daniele
2020-05-01  7:09   ` gregkh
2020-05-01  7:53     ` Daniele Alessandrelli
2020-05-01  8:04       ` gregkh

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=20200501115929.GA1609634@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=arnd@arndb.de \
    --cc=daniele.alessandrelli@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.j.murphy@intel.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox