From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754052AbbG2Tdr (ORCPT ); Wed, 29 Jul 2015 15:33:47 -0400 Received: from www.linutronix.de ([62.245.132.108]:42236 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752984AbbG2Tdq (ORCPT ); Wed, 29 Jul 2015 15:33:46 -0400 Date: Wed, 29 Jul 2015 21:33:27 +0200 (CEST) From: Thomas Gleixner To: Andy Shevchenko cc: linux-kernel@vger.kernel.org, Bjorn Helgaas , linux-pci@vger.kernel.org, Ingo Molnar , x86@kernel.org Subject: Re: [PATCH v3 0/3] x86/pci/intel-mid-pci: fix to get eMMC detected In-Reply-To: <1438161409-4671-1-git-send-email-andriy.shevchenko@linux.intel.com> Message-ID: References: <1438161409-4671-1-git-send-email-andriy.shevchenko@linux.intel.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 29 Jul 2015, Andy Shevchenko wrote: > On Intel Edison we have an interesting implementation of x86 platform without > legacy PIC and with specific PCI. There are devices which are not using > interrupt line 0, but have it assigned in the PCI configuration. By default > first come gets it, though the first eMMC host controller is the actual user > for IRQ0. > > So, this series provides a quirk (patch 1) to resolve the issue, a small fix of > error code (patch 2), and a sparse warning fix (patch 3). > > Changelog v3: > - address Thomas' comments > - massage changelog (what Thomas proposed) > > Andy Shevchenko (3): > x86/pci/intel_mid_pci: work around for IRQ0 assignment > x86/pci/intel_mid_pci: propagate actual return code > x86/pci/intel_mid_pci: fix a sparse warning I've picked them up. If you get the tip-bot mails, you might notice a few edits on the changelogs. - Sentence starts with an upper case letter. - You cannot fix a sparse warning. - "This patch does ...." is just horrible. When one reads a patch he already knows that it is a patch. Please avoid these things in the future. Thanks, tglx