From: Krzysztof Kozlowski <krzk@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] vdpa: solidrun: constify pointers to hwmon_channel_info
Date: Fri, 7 Apr 2023 19:32:20 +0200 [thread overview]
Message-ID: <de9f8156-9c68-a237-2f03-e9fe41c04beb@kernel.org> (raw)
In-Reply-To: <202304080108.n5D0MIBE-lkp@intel.com>
On 07/04/2023 19:18, kernel test robot wrote:
> Hi Krzysztof,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v6.3-rc5 next-20230406]
> [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]
Dependency is provided as link to lore, as typical in all submissions.
The --base does not make much sense since dependency is only on the lists.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-04-07 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230407150130.79917-1-krzysztof.kozlowski@linaro.org>
2023-04-07 17:18 ` [PATCH] vdpa: solidrun: constify pointers to hwmon_channel_info kernel test robot
2023-04-07 17:32 ` Krzysztof Kozlowski [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=de9f8156-9c68-a237-2f03-e9fe41c04beb@kernel.org \
--to=krzk@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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