All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH v5 0/3] Devtool: provide easy means of reconfiguring
Date: Mon, 15 Jul 2019 15:00:20 +1200	[thread overview]
Message-ID: <6626896.5blaEgOQa4@localhost.localdomain> (raw)
In-Reply-To: <1562783254-14818-1-git-send-email-chandana.kalluri@xilinx.com>

Hi Chandana

On Thursday, 11 July 2019 6:27:31 AM NZST Sai Hari Chandana Kalluri wrote:
> changelog v5
> 1. test against devtool oe-selftests and add missing function imports
> 2. rename function name from symblink_oelocal_files_srctree to 
symlink_oelocal_files_srctree
> 3. fix indendation

I'm afraid the indentation is still all over the place; however, I have taken 
the liberty of fixing it (along with a few other minor style issues) and have 
pushed the result as paule/devtool-menuconfig.

Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




      parent reply	other threads:[~2019-07-15  3:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 18:27 [master][PATCH v5 0/3] Devtool: provide easy means of reconfiguring Sai Hari Chandana Kalluri
2019-07-10 18:27 ` [master][PATCH 1/3] devtool/standard.py: Update devtool modify to copy source from work-shared if its already downloaded Sai Hari Chandana Kalluri
2019-07-10 18:27 ` [master][PATCH 2/3] devtool/standard.py: Create a copy of kernel source within work-shared if not present Sai Hari Chandana Kalluri
2019-07-10 18:27 ` [master][PATCH 3/3] devtool: provide support for devtool menuconfig command Sai Hari Chandana Kalluri
2019-07-11  5:01 ` ✗ patchtest: failure for "[master] devtool/standard.py: ..." and 2 more Patchwork
2019-07-15  3:00 ` Paul Eggleton [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=6626896.5blaEgOQa4@localhost.localdomain \
    --to=paul.eggleton@linux.intel.com \
    --cc=chandana.kalluri@xilinx.com \
    --cc=openembedded-core@lists.openembedded.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.