All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Alexander Alemayhu <alexander@alemayhu.com>, netdev@vger.kernel.org
Cc: ast@fb.com
Subject: Re: [PATCH net-next 1/3] samples/bpf: add -Wno-unknown-warning-option to clang
Date: Mon, 24 Apr 2017 16:37:41 +0200	[thread overview]
Message-ID: <58FE0DB5.20802@iogearbox.net> (raw)
In-Reply-To: <20170424133108.31595-2-alexander@alemayhu.com>

On 04/24/2017 03:31 PM, Alexander Alemayhu wrote:
> I was initially going to remove '-Wno-address-of-packed-member' because I
> thought it was not supposed to be there but Daniel suggested using
> '-Wno-unknown-warning-option'.
>
> This silences several warnings similiar to the one below
>
> warning: unknown warning option '-Wno-address-of-packed-member' [-Wunknown-warning-option]
> 1 warning generated.

Yeah, that feature seems fairly new (Feb 2017 accepted if I
see this correctly): https://reviews.llvm.org/D20561

Given the -Wno-address-of-packed-member was there to silence
warnings in the first place, we should also silence warnings
when -Wno-address-of-packed-member is unknown to clang/llvm.

[...]
>
> Signed-off-by: Alexander Alemayhu <alexander@alemayhu.com>

Acked-by: Daniel Borkmann <daniel@iogearbox.net>

  reply	other threads:[~2017-04-24 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 13:31 [PATCH net-next 0/3] Misc BPF cleanup Alexander Alemayhu
2017-04-24 13:31 ` [PATCH net-next 1/3] samples/bpf: add -Wno-unknown-warning-option to clang Alexander Alemayhu
2017-04-24 14:37   ` Daniel Borkmann [this message]
2017-04-24 13:31 ` [PATCH net-next 2/3] samples/bpf: add static to function with no prototype Alexander Alemayhu
2017-04-24 14:40   ` Daniel Borkmann
2017-04-24 13:31 ` [PATCH net-next 3/3] samples/bpf: check before defining offsetof Alexander Alemayhu
2017-04-24 14:41   ` Daniel Borkmann
2017-04-25 14:27     ` David Laight
2017-04-26  5:17       ` Alexander Alemayhu
2017-04-24 14:45 ` [PATCH net-next 0/3] Misc BPF cleanup Alexei Starovoitov
2017-04-24 20:20 ` David Miller

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=58FE0DB5.20802@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexander@alemayhu.com \
    --cc=ast@fb.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.