linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Stefano Brivio <sbrivio@redhat.com>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: mmotm 2021-05-19-23-58 uploaded (net/netfilter/nft_set_pipapo_avx2.c)
Date: Thu, 20 May 2021 15:40:54 -0700	[thread overview]
Message-ID: <3d718861-28bd-dd51-82d4-96b040aa1ab4@infradead.org> (raw)
In-Reply-To: <20210520065918.KsmugQp47%akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On 5/19/21 11:59 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2021-05-19-23-58 has been uploaded to
> 
>    https://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> https://www.ozlabs.org/~akpm/mmotm/
> 
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> 
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
> 
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
> 
> This tree is partially included in linux-next.  To see which patches are
> included in linux-next, consult the `series' file.  Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.

on x86_64:
(from linux-next, not mmotm)

../net/netfilter/nft_set_pipapo_avx2.c: In function ‘nft_pipapo_avx2_lookup’:
../net/netfilter/nft_set_pipapo_avx2.c:1135:10: error: implicit declaration of function ‘nft_pipapo_lookup’; did you mean ‘nft_pipapo_avx2_lookup’? [-Werror=implicit-function-declaration]
   return nft_pipapo_lookup(net, set, key, ext);
          ^~~~~~~~~~~~~~~~~

Full randconfig file is attached.

-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>


[-- Attachment #2: config-r9445.gz --]
[-- Type: application/gzip, Size: 37684 bytes --]

  parent reply	other threads:[~2021-05-20 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  6:59 mmotm 2021-05-19-23-58 uploaded akpm
2021-05-20 22:21 ` mmotm 2021-05-19-23-58 uploaded (mm/migrate.c) Randy Dunlap
2021-05-21  2:22   ` [External] " Muchun Song
2021-05-20 22:40 ` Randy Dunlap [this message]
2021-05-20 23:07   ` mmotm 2021-05-19-23-58 uploaded (net/netfilter/nft_set_pipapo_avx2.c) Stephen Rothwell
2021-05-21  1:04     ` Randy Dunlap
2021-05-20 22:53 ` mmotm 2021-05-19-23-58 uploaded (drivers/iio/accel/fxls8962af-core.o) Randy Dunlap
2021-05-21  9:00   ` Sean Nyekjaer

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=3d718861-28bd-dd51-82d4-96b040aa1ab4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=coreteam@netfilter.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sbrivio@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).