All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qian Lei <qianl.fnst@cn.fujitsu.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] UMIP: add new recipe
Date: Tue, 25 Nov 2014 17:23:29 +0800	[thread overview]
Message-ID: <20141125172329.21e1caea@Fedora> (raw)
In-Reply-To: <20141121141904.GK2163@jama>

On Fri, 21 Nov 2014 15:19:04 +0100
Martin Jansa <martin.jansa@gmail.com> wrote:

 
> It's failing to build in my world builds, so please wait a bit more.
> 
> Also a lot of patches from last week were modified when I was
> cherry-picking them to master-next, please make sure you're using right
> version.

Hi Jansa:
  Could you show me the error message when you compile the umip? It is OK
in my system and I can not reproduce the bug. I use poky 1.7 and following
is my step:
    1) copy umip and indent to poky/meta/recipes-myrecipe/
    2) source oe-init-build-env build-arm
    3) modify the MACHINE in build-arm/conf/local.conf to "qemuarm"
    4) bitbake umip
Is there something wrong?

  In addition, what's the correct workflow for developers/maintainers? I
meaning if I want to send patches to community, what extra tests should I
do to make them more reliable and containing less error, such as compiling
error, dependence error or something else, although the patches are OK in
our build environment.
  And as you, the maintainer, how to test a new patch and what's the standard
for patches which could be merge into some branch? I need more detail info to
improve my patches' quality.

Thanks.

-- 
Qian Lei


  parent reply	other threads:[~2014-11-25  9:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  9:51 [PATCH] umip: Add new recipes Qian Lei
2014-11-19 15:49 ` Martin Jansa
2014-11-21  7:55   ` [PATCH v2 0/2] Add new recipe UMIP & Indent Qian Lei
2014-11-21  7:55     ` [PATCH v2 1/2] UMIP: add new recipe Qian Lei
2014-11-21 14:06       ` Joe MacDonald
2014-11-21 14:19         ` Martin Jansa
2014-11-21 14:46           ` Joe MacDonald
2014-11-25  9:23           ` Qian Lei [this message]
2014-11-21  7:55     ` [PATCH v2 2/2] Indent: Add " Qian Lei
2014-11-21  9:52       ` Martin Jansa
2014-11-24  5:21     ` [PATCH v3 1/2] indent: " Qian Lei
2014-11-24  5:28       ` [PATCH v3 2/2] UMIP: add " Qian Lei

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=20141125172329.21e1caea@Fedora \
    --to=qianl.fnst@cn.fujitsu.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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.