From: Sedat Dilek <sedat.dilek@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Willy Tarreau <w@1wt.eu>, 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 21:41:00 +0200 [thread overview]
Message-ID: <CA+icZUUo1PYQ6EjwsK=meBrXnxyxrC_PtY2qe4L3BM2MdO6=Gg@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wg8t3S3kWjzTywO5RTv4QrTSYYapEw10kFgD-dRLt08ug@mail.gmail.com>
On Thu, Jun 9, 2022 at 9:34 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Thu, Jun 9, 2022 at 12:32 PM Willy Tarreau <w@1wt.eu> wrote:
> >
> > Finally we did better and disabled engines completely!
>
> Some day that fix will make it to me, and I can remove that ugly pragma.
>
For the part scripts/sign-file.c - you looked at...?
https://lore.kernel.org/lkml/20220518215129.264872-1-keescook@chromium.org/
-Sedat-
prev parent reply other threads:[~2022-06-09 19:41 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
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 [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='CA+icZUUo1PYQ6EjwsK=meBrXnxyxrC_PtY2qe4L3BM2MdO6=Gg@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--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=tasmiya@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--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.