All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	keyrings@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Salvatore Bonaccorso <carnil@debian.org>,
	David Woodhouse <dwmw2@infradead.org>,
	David Howells <dhowells@redhat.com>,
	Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [Linux v5.17.9] -Wdeprecated-declarations warnings with LLVM-14 and OpenSSL v3.0.x
Date: Thu, 9 Jun 2022 12:25:31 -0700	[thread overview]
Message-ID: <CAHk-=wimC_B+nCJrXwuvWULz6ycFFmRMT1Uc+PeM5wJdma_VFw@mail.gmail.com> (raw)
In-Reply-To: <20220609192308.GB10732@1wt.eu>

On Thu, Jun 9, 2022 at 12:23 PM Willy Tarreau <w@1wt.eu> wrote:
>
> IIRC you can also disable the deprecation warnings by defining the
> OPENSSL_SUPPRESS_DEPRECATED macro. It doesn't require to change the
> compiler's options and allows us to put our head in the sand.

That one had the downside that you have to know what you're doing to
make such a change ;)

I just wanted to be able to start doing pulls again after mistakenly
thinking that an upgrade would be pain-free.

                    Linus

  reply	other threads:[~2022-06-09 19:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  9:55 [Linux v5.17.9] -Wdeprecated-declarations warnings with LLVM-14 and OpenSSL v3.0.x Sedat Dilek
2022-05-19 10:01 ` Sedat Dilek
2022-05-24 19:13   ` Sedat Dilek
2022-05-27  7:47     ` Sedat Dilek
2022-05-27 16:05       ` Sedat Dilek
2022-06-09 18:40         ` Sedat Dilek
2022-06-09 19:04           ` Linus Torvalds
2022-06-09 19:19             ` Sedat Dilek
2022-06-09 19:23               ` Willy Tarreau
2022-06-09 19:25                 ` Linus Torvalds [this message]
2022-06-09 19:31                   ` Sedat Dilek
2022-06-22 18:37                     ` Andres Freund
2022-08-06  7:42                       ` Sedat Dilek
2022-06-09 19:32                   ` Willy Tarreau
2022-06-09 19:34                     ` Linus Torvalds
2022-06-09 19:41                       ` Sedat Dilek

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='CAHk-=wimC_B+nCJrXwuvWULz6ycFFmRMT1Uc+PeM5wJdma_VFw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=carnil@debian.org \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=keescook@chromium.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=tasmiya@linux.vnet.ibm.com \
    --cc=w@1wt.eu \
    /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.