From: sathyanarayanan kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, sathyaosid@gmail.com
Subject: Re: [PATCH v2 1/1] mtd: intel-spi: Add Intel Lewisburg PCH SPI super SKU PCI ID
Date: Mon, 30 Oct 2017 15:28:46 -0700 [thread overview]
Message-ID: <754005b2-fea7-91f3-b526-c325de2ad6bf@linux.intel.com> (raw)
In-Reply-To: <ae3620ec-293e-458e-76b1-5c13e0cdc992@wedev4u.fr>
Hi,
On 10/30/2017 03:58 AM, Cyrille Pitchen wrote:
> Applied to the spi-nor/next branch of l2-mtd
>
> Just for info, this patch didn't apply directly, it misses a line in the list of
> PCI IDS:
>
> { PCI_VDEVICE(INTEL, 0x18e0), (unsigned long)&bxt_info },
I re-based my patch on top of Mika's SPI support patch. And it applied
cleanly on top of 4.14-rc6 kernel. Not sure where the problem was?
http://git.infradead.org/l2-mtd.git/commitdiff/d92b0f18a2039ff736b4296ad3cf3d505512051e
--
Sathyanarayanan Kuppuswamy
Linux kernel developer
next prev parent reply other threads:[~2017-10-30 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 9:57 [PATCH v1 1/1] mtd: intel-spi: Add support for Intel Lewisburg SPI serial flash controller sathyanarayanan.kuppuswamy
2017-10-29 10:09 ` Marek Vasut
2017-10-29 10:16 ` Mika Westerberg
2017-10-29 10:34 ` Marek Vasut
2017-10-29 19:18 ` Kuppuswamy, Sathyanarayanan
2017-10-29 19:58 ` Mika Westerberg
2017-10-29 22:17 ` [PATCH v2 1/1] mtd: intel-spi: Add Intel Lewisburg PCH SPI super SKU PCI ID sathyanarayanan.kuppuswamy
2017-10-30 7:32 ` Mika Westerberg
2017-10-30 10:58 ` Cyrille Pitchen
2017-10-30 14:16 ` Andy Shevchenko
2017-10-30 22:28 ` sathyanarayanan kuppuswamy [this message]
2017-10-31 7:48 ` Mika Westerberg
2017-10-29 19:14 ` [PATCH v1 1/1] mtd: intel-spi: Add support for Intel Lewisburg SPI serial flash controller Kuppuswamy, Sathyanarayanan
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=754005b2-fea7-91f3-b526-c325de2ad6bf@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=sathyaosid@gmail.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 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.