From: Petr Machata <petrm@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: Petr Machata <petrm@nvidia.com>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>
Subject: Re: [PATCH net-next 2/8] ndo_fdb_add: Shift responsibility for notifying to drivers
Date: Thu, 24 Oct 2024 12:05:24 +0200 [thread overview]
Message-ID: <87frolizmr.fsf@nvidia.com> (raw)
In-Reply-To: <202410240831.djzzgAk3-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202410240831.djzzgAk3-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c:427:19: error: use of undeclared identifier 'dev'
> 427 | rtnl_fdb_notify(dev, addr, vid, RTM_NEWNEIGH, ndm->ndm_state);
> | ^
> drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c:2440:46: warning: shift count >= width of type [-Wshift-count-overflow]
> 2440 | err = dma_set_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(64));
> | ^~~~~~~~~~~~~~~~
> include/linux/dma-mapping.h:77:54: note: expanded from macro 'DMA_BIT_MASK'
> 77 | #define DMA_BIT_MASK(n) (((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))
> | ^ ~~~
> 1 warning and 1 error generated.
Hm, evidently I forgot to enable qlcnic in my test build. My bad, will
fix & resend.
prev parent reply other threads:[~2024-10-24 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00caa74f6dea128400472b5dec77f61b16d0f9d4.1729607879.git.petrm@nvidia.com>
2024-10-24 0:08 ` [PATCH net-next 2/8] ndo_fdb_add: Shift responsibility for notifying to drivers kernel test robot
2024-10-24 10:05 ` Petr Machata [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=87frolizmr.fsf@nvidia.com \
--to=petrm@nvidia.com \
--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