mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jagannadha Sutradharudu Teki  <jagannadha.sutradharudu-teki@xilinx.com>
To: Joe Perches <joe@perches.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@canonical.com>
Subject: RE: [PATCH] checkpatch: Do not hardcode perl path
Date: Fri, 6 Dec 2013 06:04:37 +0000	[thread overview]
Message-ID: <1c130cef-3be7-408c-867b-5a3de863a831@DB9EHSMHS016.ehs.local> (raw)
In-Reply-To: <1386273109.10003.12.camel@joe-AO722>

> -----Original Message-----
> From: Joe Perches [mailto:joe@perches.com]
> Sent: Friday, December 06, 2013 1:22 AM
> To: Jagannadha Sutradharudu Teki
> Cc: linux-kernel@vger.kernel.org; Andy Whitcroft; Jagannadha Sutradharudu
> Teki
> Subject: Re: [PATCH] checkpatch: Do not hardcode perl path
>
> On Thu, 2013-12-05 at 16:53 +0530, Jagannadha Sutradharudu Teki wrote:
> > checkpatch.pl requires perl v5.10.0 to run but it doesn't require to
> > place in /usr/bin/perl Use env to ensure that the interpreter used is
> > the first one on environment's $PATH on system with several versions
> > of perl installed.
>
> I don't have an opinion on this patch.

fyi: I have some notes here - this change will took the perl bin(if user explicitly use perl instead of from /usr/bin/perl) from bashrc instead of taking /usr/bin/perl all the time.

Jagan.



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.



      reply	other threads:[~2013-12-06  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 11:23 Jagannadha Sutradharudu Teki
2013-12-05 19:51 ` Joe Perches
2013-12-06  6:04   ` Jagannadha Sutradharudu Teki [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=1c130cef-3be7-408c-867b-5a3de863a831@DB9EHSMHS016.ehs.local \
    --to=jagannadha.sutradharudu-teki@xilinx.com \
    --cc=apw@canonical.com \
    --cc=joe@perches.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

all inboxes | Powered by JetHome®