From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: RE: [PATCH] namespace: fix namespace.pl script to support relative paths
Date: Fri, 27 Sep 2019 23:30:54 +0000 [thread overview]
Message-ID: <02874ECE860811409154E81DA85FBB58968DBE54@ORSMSX121.amr.corp.intel.com> (raw)
In-Reply-To: <7b26e6cc-10ce-5df2-6375-1f95bc4da04e@infradead.org>
> -----Original Message-----
> From: Randy Dunlap [mailto:rdunlap@infradead.org]
> Sent: Friday, September 27, 2019 4:12 PM
> To: Keller, Jacob E <jacob.e.keller@intel.com>
> Cc: intel-wired-lan@lists.osuosl.org; linux-kernel@vger.kernel.org; linux-kbuild <linux-
> kbuild@vger.kernel.org>; Masahiro Yamada <yamada.masahiro@socionext.com>
> Subject: Re: [PATCH] namespace: fix namespace.pl script to support relative paths
>
>
> re: https://lore.kernel.org/lkml/20190129204319.15238-1-jacob.e.keller@intel.com/
>
> Did anything happen with this patch?
>
> Please send it to linux-kbuild@vger.kernel.org and
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
>
> You can also add:
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
>
>
> I was just about to fix this script but I decided to first see if anyone else
> had already done so. Thanks.
>
> --
> ~Randy
Done, thanks.
Regards,
Jake
next prev parent reply other threads:[~2019-09-27 23:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 20:43 [PATCH] namespace: fix namespace.pl script to support relative paths Jacob Keller
2019-09-27 23:12 ` Randy Dunlap
2019-09-27 23:23 ` Keller, Jacob E
2019-09-27 23:30 ` Keller, Jacob E [this message]
2019-09-29 0:20 ` Masahiro Yamada
2019-09-30 19:46 ` Keller, Jacob E
2019-10-23 5:21 ` Masahiro Yamada
2019-10-23 21:34 ` Keller, Jacob E
2019-10-24 1:21 ` Masahiro Yamada
2019-10-25 17:45 ` Keller, Jacob E
2019-10-25 19:30 ` Randy Dunlap
2019-10-25 20:20 ` Keller, Jacob E
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=02874ECE860811409154E81DA85FBB58968DBE54@ORSMSX121.amr.corp.intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=yamada.masahiro@socionext.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).