From: Arnd Bergmann <arnd@arndb.de>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-arch <linux-arch@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH] asm-generic: make simd.h a mandatory include/asm header
Date: Mon, 29 Jul 2019 14:19:04 +0200 [thread overview]
Message-ID: <CAK8P3a2sa4DZyArsRNh-MMqL2dLv32-pgZhH+VdE8X2UKFjZTg@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu_8nNd-td5F9u0dgH7x1kF+r8sCL432MvzmxqNZqqW-gA@mail.gmail.com>
On Mon, Jul 29, 2019 at 12:45 PM Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> On Mon, 29 Jul 2019 at 13:32, Arnd Bergmann <arnd@arndb.de> wrote:
> > It looks like there are a number of these that could be handled the
> > same way. Should we do that for the asm-generic tree afterwards?
> >
>
> I guess it depends whether any dependencies on those headers exist in
> code that is truly generic. If they are only needed by some common
> infrastructure that cannot be enabled for a certain architecture
> anyway, I don't think making it a mandatory header is appropriate.
>
> So I think the question is whether the first column and the number of
> per-arch instances of that header add up to 25 (disregarding the
> exception for arch/um for now)
Here is a list of how many architectures besides arch/um do not have a
given file
with either generic-y or as a private copy:
$ git grep -h generic-y arch/*/include/asm/Kbuild | sort | uniq -c |
sort -nr | cut -f 2 -d= | while read file ; do for arch in
arch/*/include/asm ; do if [ ! -e ${arch}/${file} ] && ! grep -q
${file} ${arch}/Kbuild ; then echo ${arch}/${file} ; fi ; done | grep
-v arch/um/ | echo `wc -l` $file ; done | sort -n
0 atomic.h
0 barrier.h
0 bitops.h
0 bug.h
0 bugs.h
0 cacheflush.h
0 checksum.h
0 compat.h
0 current.h
0 delay.h
0 device.h
0 div64.h
0 dma.h
0 dma-mapping.h
0 emergency-restart.h
0 exec.h
0 fb.h
0 ftrace.h
0 futex.h
0 hardirq.h
0 hw_irq.h
0 io.h
0 irq.h
0 irq_regs.h
0 irq_work.h
0 kdebug.h
0 kmap_types.h
0 kprobes.h
0 linkage.h
0 local.h
0 mm-arch-hooks.h
0 mmiowb.h
0 mmu_context.h
0 mmu.h
0 module.h
0 pci.h
0 percpu.h
0 pgalloc.h
0 preempt.h
0 sections.h
0 serial.h
0 shmparam.h
0 switch_to.h
0 timex.h
0 tlbflush.h
0 topology.h
0 trace_clock.h
0 uaccess.h
0 unaligned.h
0 vga.h
0 word-at-a-time.h
0 xor.h
1 asm-offsets.h
1 cmpxchg.h
1 spinlock.h
1 user.h
2 kvm_para.h
3 mcs_spinlock.h
4 extable.h
4 local64.h
9 parport.h
12 syscalls.h
13 param.h
14 seccomp.h
15 export.h
16 dma-contiguous.h
16 flat.h
16 msi.h
17 qrwlock.h
18 gpio.h
18 qspinlock.h
20 early_ioremap.h
20 set_memory.h
20 simd.h
20 vmlinux.lds.h
21 vtime.h
22 iomap.h
23 qrwlock_types.h
23 qspinlock_types.h
24 bpf_perf_event.h
Arnd
prev parent reply other threads:[~2019-07-29 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 9:55 [PATCH] asm-generic: make simd.h a mandatory include/asm header Ard Biesheuvel
2019-07-29 10:32 ` Arnd Bergmann
2019-07-29 10:45 ` Ard Biesheuvel
2019-07-29 12:19 ` Arnd Bergmann [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=CAK8P3a2sa4DZyArsRNh-MMqL2dLv32-pgZhH+VdE8X2UKFjZTg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=ard.biesheuvel@linaro.org \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).