All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] thunderbolt fixes for v4.15-rc2
Date: Fri,  1 Dec 2017 15:08:02 +0300	[thread overview]
Message-ID: <20171201120805.60852-1-mika.westerberg@linux.intel.com> (raw)

Hi Greg,

Here are two Thunderbolt fixes and one related MAINTAINERS update for the
next -rc:

- Use shorter path for force_power attribute in thunderbolt.rst
- Ring interrupts were not masked properly when Rx polling starts
- Add thunderbolt.rst to the Thunderbolt driver MAINTAINERS entry

Thanks!

Andy Shevchenko (1):
  thunderbolt: Make pathname to force_power shorter

Mika Westerberg (2):
  MAINTAINERS: Add thunderbolt.rst to the Thunderbolt driver entry
  thunderbolt: Mask ring interrupt properly when polling starts

 Documentation/admin-guide/thunderbolt.rst | 2 +-
 MAINTAINERS                               | 1 +
 drivers/thunderbolt/nhi.c                 | 2 +-
 3 files changed, 3 insertions(+), 2 deletions(-)

-- 
2.15.0

             reply	other threads:[~2017-12-01 12:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 12:08 Mika Westerberg [this message]
2017-12-01 12:08 ` [PATCH 1/3] thunderbolt: Make pathname to force_power shorter Mika Westerberg
2017-12-01 12:08 ` [PATCH 2/3] MAINTAINERS: Add thunderbolt.rst to the Thunderbolt driver entry Mika Westerberg
2017-12-01 12:08 ` [PATCH 3/3] thunderbolt: Mask ring interrupt properly when polling starts Mika Westerberg
2017-12-05  8:49 ` [PATCH 0/3] thunderbolt fixes for v4.15-rc2 Mika Westerberg
2017-12-05  8:52   ` Greg Kroah-Hartman
2017-12-16  8:50     ` Mika Westerberg
2017-12-16 16:11       ` Greg Kroah-Hartman

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=20171201120805.60852-1-mika.westerberg@linux.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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.