From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Shishkin <alexander.shishkin@intel.com>
Cc: linux-kernel@vger.kernel.org, alexander.shishkin@linux.intel.com
Subject: Re: [GIT PULL] intel_th: Fixes for char-misc-linus
Date: Wed, 26 Jul 2017 07:39:35 -0700 [thread overview]
Message-ID: <20170726143935.GB12969@kroah.com> (raw)
In-Reply-To: <87379jv008.fsf@ashishki-desk.ger.corp.intel.com>
On Wed, Jul 26, 2017 at 03:46:47PM +0300, Alexander Shishkin wrote:
> Hi Greg,
>
> Here are my fixes for 4.13, please consider pulling. These are really
> just two new PCI IDs. Thanks!
>
> The following changes since commit 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9:
>
> Linux 4.13-rc2 (2017-07-23 16:15:17 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git tags/stm-fixes-for-greg-20170726
>
> for you to fetch changes up to a45ae3526897ebcd128e9044040bc7b4f57de4f0:
>
> intel_th: pci: Add Cannon Lake PCH-LP support (2017-07-26 15:33:15 +0300)
>
> ----------------------------------------------------------------
> intel_th: Fixes for v4.13
>
> These are two new PCI IDs (Cannon Lake PCH-H and PCH-LP).
>
> ----------------------------------------------------------------
> Alexander Shishkin (2):
> intel_th: pci: Add Cannon Lake PCH-H support
> intel_th: pci: Add Cannon Lake PCH-LP support
Why not just send me two patches? Would be much easier than a pull
request...
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-26 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 12:46 [GIT PULL] intel_th: Fixes for char-misc-linus Alexander Shishkin
2017-07-26 14:39 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 13:00 Alexander Shishkin
2017-03-16 1:47 ` Greg KH
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=20170726143935.GB12969@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.shishkin@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.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