From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <yehezkel.bernat@intel.com>
Subject: Re: [PATCH 1/2] MAINTAINERS: Add thunderbolt.rst to the Thunderbolt driver entry
Date: Fri, 1 Dec 2017 11:40:46 +0200 [thread overview]
Message-ID: <20171201094046.GK22431@lahna.fi.intel.com> (raw)
In-Reply-To: <20171127114858.20893-1-mika.westerberg@linux.intel.com>
On Mon, Nov 27, 2017 at 02:48:57PM +0300, Mika Westerberg wrote:
> Make sure Thunderbolt maintainers get to see patches that touch
> documentation of the Thunderbolt driver as well.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied.
prev parent reply other threads:[~2017-12-01 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 11:48 [PATCH 1/2] MAINTAINERS: Add thunderbolt.rst to the Thunderbolt driver entry Mika Westerberg
2017-11-27 11:48 ` [PATCH 2/2] thunderbolt: Mask ring interrupt properly when polling starts Mika Westerberg
2017-11-27 16:21 ` Bernat, Yehezkel
2017-12-01 9:49 ` mika.westerberg
2017-12-01 9:40 ` Mika Westerberg [this message]
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=20171201094046.GK22431@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=yehezkel.bernat@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox