Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 1 May 2020 13:59:29 +0200
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
Message-ID: <20200501115929.GA1609634@kroah.com>
References: <cover.1587485099.git.daniele.alessandrelli@intel.com>
 <13ca92165fab2827b6d439661e75f5b91ef083c2.1587485099.git.daniele.alessandrelli@intel.com>
 <20200501081002.GA1055721@kroah.com>
 <f60aece195cd0700728fc38b0398949a82b72fc3.camel@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f60aece195cd0700728fc38b0398949a82b72fc3.camel@linux.intel.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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