From: Chen, Rong A <rong.a.chen@intel.com>
To: kbuild@lists.01.org
Subject: Re: [jlayton:ceph-fscache-iter 76/77] fs/ceph/addr.c:225 ceph_fsreq_issue_op() error: uninitialized symbol 'err'.
Date: Sun, 31 May 2020 21:21:37 +0800 [thread overview]
Message-ID: <a3be6b48-791d-617f-3254-db2eda2f2154@intel.com> (raw)
In-Reply-To: <20200530214428.GS22511@kadam>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On 5/31/2020 5:44 AM, Dan Carpenter wrote:
> On Sat, May 30, 2020 at 04:49:40PM -0400, Jeff Layton wrote:
>> I wonder -- is there a way to name my branches so that they don't get
>> picked up by the 0-day service? I generally like the testing, but when I
>> still have a branch that's not yet fully baked it's probably a bit of
>> waste. Maybe if we could prefix it with "wip-" or something?
> It doesn't take time from me. You can ignore the Reported-by tags for
> new devel work, no one will be offended.
>
> There is a way to disable it but I forget how. It should probably be
> added to the FAQ. https://01.org/lkp/documentation/0-day-test-service
Hi all,
We have a FAQ for this: https://github.com/intel/lkp-tests/wiki/LKP-FAQ
Best Regards,
Rong Chen
WARNING: multiple messages have this Message-ID (diff)
From: Chen, Rong A <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [kbuild] Re: [jlayton:ceph-fscache-iter 76/77] fs/ceph/addr.c:225 ceph_fsreq_issue_op() error: uninitialized symbol 'err'.
Date: Sun, 31 May 2020 21:21:37 +0800 [thread overview]
Message-ID: <a3be6b48-791d-617f-3254-db2eda2f2154@intel.com> (raw)
In-Reply-To: <20200530214428.GS22511@kadam>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On 5/31/2020 5:44 AM, Dan Carpenter wrote:
> On Sat, May 30, 2020 at 04:49:40PM -0400, Jeff Layton wrote:
>> I wonder -- is there a way to name my branches so that they don't get
>> picked up by the 0-day service? I generally like the testing, but when I
>> still have a branch that's not yet fully baked it's probably a bit of
>> waste. Maybe if we could prefix it with "wip-" or something?
> It doesn't take time from me. You can ignore the Reported-by tags for
> new devel work, no one will be offended.
>
> There is a way to disable it but I forget how. It should probably be
> added to the FAQ. https://01.org/lkp/documentation/0-day-test-service
Hi all,
We have a FAQ for this: https://github.com/intel/lkp-tests/wiki/LKP-FAQ
Best Regards,
Rong Chen
next prev parent reply other threads:[~2020-05-31 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 20:44 [jlayton:ceph-fscache-iter 76/77] fs/ceph/addr.c:225 ceph_fsreq_issue_op() error: uninitialized symbol 'err' Dan Carpenter
2020-05-30 20:44 ` [kbuild] " Dan Carpenter
2020-05-30 20:49 ` Jeff Layton
2020-05-30 21:44 ` Dan Carpenter
2020-05-30 21:44 ` [kbuild] " Dan Carpenter
2020-05-31 13:21 ` Chen, Rong A [this message]
2020-05-31 13:21 ` [kbuild] " Chen, Rong A
-- strict thread matches above, loose matches on Subject: below --
2020-05-30 19:59 kbuild test robot
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=a3be6b48-791d-617f-3254-db2eda2f2154@intel.com \
--to=rong.a.chen@intel.com \
--cc=kbuild@lists.01.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.