From: "Kershner, David A" <David.Kershner@unisys.com>
To: Tom Saeger <tom.saeger@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
*S-Par-Maintainer <SParMaintainer@unisys.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 1/1] staging: Fix incorrect unisys MAINTAINERS pattern
Date: Tue, 31 Oct 2017 19:31:07 +0000 [thread overview]
Message-ID: <CY4PR07MB3176CA38ABA695414D554A00F05E0@CY4PR07MB3176.namprd07.prod.outlook.com> (raw)
In-Reply-To: <de252c5f08c36650b133a2091ad99ea8ef312da6.1509463486.git.tom.saeger@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
> -----Original Message-----
> From: Tom Saeger [mailto:tom.saeger@oracle.com]
> Sent: Tuesday, October 31, 2017 11:30 AM
> To: Kershner, David A <David.Kershner@unisys.com>; Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>; *S-Par-Maintainer
> <SParMaintainer@unisys.com>; devel@driverdev.osuosl.org; linux-
> kernel@vger.kernel.org
> Cc: Tom Saeger <tom.saeger@oracle.com>
> Subject: [PATCH v2 1/1] staging: Fix incorrect unisys MAINTAINERS pattern
>
> Fix stale path to documentation in MAINTAINERS file.
>
> Signed-off-by: Tom Saeger <tom.saeger@oracle.com>
> Cc: David Kershner <david.kershner@unisys.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: David Kershner <david.kershne@unisys.com>
> ---
> drivers/staging/unisys/MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/unisys/MAINTAINERS
> b/drivers/staging/unisys/MAINTAINERS
> index 1f0425bf3583..aaddc619c329 100644
> --- a/drivers/staging/unisys/MAINTAINERS
> +++ b/drivers/staging/unisys/MAINTAINERS
> @@ -1,5 +1,5 @@
> Unisys s-Par drivers
> M: David Kershner <sparmaintainer@unisys.com>
> S: Maintained
> -F: Documentation/s-Par/overview.txt
> +F: drivers/staging/unisys/Documentation/overview.txt
> F: drivers/staging/unisys/
> --
> 2.14.3
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7862 bytes --]
prev parent reply other threads:[~2017-10-31 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 15:30 [PATCH v2 1/1] staging: Fix incorrect unisys MAINTAINERS pattern Tom Saeger
2017-10-31 19:31 ` Kershner, David A [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=CY4PR07MB3176CA38ABA695414D554A00F05E0@CY4PR07MB3176.namprd07.prod.outlook.com \
--to=david.kershner@unisys.com \
--cc=SParMaintainer@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.saeger@oracle.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;
as well as URLs for NNTP newsgroup(s).