From: Linus Torvalds <torvalds@linux-foundation.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
sedat.dilek@credativ.de, Jean Delvare <jdelvare@suse.de>,
linux-i2c@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
pmac@au1.ibm.com
Subject: Re: [PATCH v2] i2c: Remove '-Wno-deprecated-declarations' compiler warning
Date: Mon, 20 Aug 2018 13:36:55 -0700 [thread overview]
Message-ID: <CA+55aFy+vVH4Mb-unrxm72JNORdxHaCFYEhD8iXbxo-OW0f8qg@mail.gmail.com> (raw)
In-Reply-To: <20180820080629.i7y4cx4wewmcyqpk@ninjato>
On Mon, Aug 20, 2018 at 1:06 AM Wolfram Sang <wsa@the-dreams.de> wrote:
>
> [1] http://patchwork.ozlabs.org/patch/461759/
Let's just apply this.
If it breaks something and somebody notices, we'll at least have found a tester.
And if it doesn't break anything, or if nobody ever notices the
breakage, then we will have gotten rid of that deprecated function.
Either way we win. There's no downside.
Wolfram, should I just take that patch as-is and get rid of the
deprecated atach_adapter thing, or will you send me a pull request?
Linus
next prev parent reply other threads:[~2018-08-20 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 13:51 [PATCH v2] i2c: Remove '-Wno-deprecated-declarations' compiler warning Sedat Dilek
2018-08-19 15:23 ` kbuild test robot
2018-08-19 16:46 ` Linus Torvalds
2018-08-20 2:12 ` Benjamin Herrenschmidt
2018-08-20 8:06 ` Wolfram Sang
2018-08-20 11:25 ` Benjamin Herrenschmidt
2018-08-20 20:36 ` Linus Torvalds [this message]
2018-08-21 2:04 ` Wolfram Sang
2018-08-24 13:01 ` Wolfram Sang
2018-08-24 13:49 ` Sedat Dilek
2018-08-24 14:07 ` Wolfram Sang
2018-08-24 14:19 ` Sedat Dilek
2018-08-24 15:01 ` Wolfram Sang
2018-08-24 15:03 ` 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=CA+55aFy+vVH4Mb-unrxm72JNORdxHaCFYEhD8iXbxo-OW0f8qg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=pmac@au1.ibm.com \
--cc=sedat.dilek@credativ.de \
--cc=wsa@the-dreams.de \
/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).