From: "Luís Henriques" <lhenriques@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Xiubo Li <xiubli@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
oe-kbuild-all@lists.linux.dev, ceph-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ceph: fix memory leak in mount error path when using test_dummy_encryption
Date: Fri, 4 Nov 2022 09:47:03 +0000 [thread overview]
Message-ID: <Y2TflzMdeiXRMoek@suse.de> (raw)
In-Reply-To: <202211042241.mPJd6rKy-lkp@intel.com>
On Fri, Nov 04, 2022 at 02:40:25PM +0800, kernel test robot wrote:
> Hi Luís,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on ceph-client/for-linus]
> [also build test ERROR on linus/master v6.1-rc3 next-20221104]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Lu-s-Henriques/ceph-fix-memory-leak-in-mount-error-path-when-using-test_dummy_encryption/20221103-233629
> base: https://github.com/ceph/ceph-client.git for-linus
Well, thank you very much! Now, how do I tell this bot that this patch
isn't targeting this branch?
Cheers,
--
Luís
next prev parent reply other threads:[~2022-11-04 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:36 [PATCH] ceph: fix memory leak in mount error path when using test_dummy_encryption Luís Henriques
2022-11-04 6:40 ` kernel test robot
2022-11-04 9:47 ` Luís Henriques [this message]
2022-11-04 10:02 ` Chen, Rong A
2022-11-04 11:21 ` Luís Henriques
2022-11-04 14:05 ` kernel test robot
2022-11-07 7:47 ` Xiubo Li
2022-11-07 10:23 ` Luís Henriques
2022-11-07 11:06 ` Xiubo Li
2022-11-07 14:19 ` Luís Henriques
2022-11-08 5:56 ` Xiubo Li
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=Y2TflzMdeiXRMoek@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xiubli@redhat.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