From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Petr Mladek <pmladek@suse.com>,
Tejun Heo <tj@kernel.org>, Steven Rostedt <rostedt@goodmis.org>,
Dave Young <dyoung@redhat.com>, Andi Kleen <ak@linux.intel.com>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
adi-buildroot-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] dump_stack: convert generic dump_stack into a weak symbol
Date: Wed, 7 Mar 2018 23:41:42 +1100 [thread overview]
Message-ID: <20180307234142.1c7d2710@canb.auug.org.au> (raw)
In-Reply-To: <20180307114845.GA894@jagdpanzerIV>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Hi Sergey,
On Wed, 7 Mar 2018 20:48:56 +0900 Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote:
>
> On (03/07/18 11:57), Arnd Bergmann wrote:
> [..]
> > >> Originally I planned to wait a few more releases, but the last maintainer
> > >> has commented that he will now send a patch for immediate removal,
> > >> so 4.17 is almost certain at this point.
> > >
> > > Would be great to get it removed as soon as possible then. Otherwise we
> > > will get broken blackfin build errors from Stephen (or would need to hold
> > > off Dave's patch).
> >
> > You could also add a patch to your tree that removes the blackfin
> > dump_stack() function, or we could ask Stephen and the other
> > people operating build bots to stop building blackfin right now
> > (they will have to do that anyway once the arch gets removed).
>
> OK. Petr, Stephen, what would be your preference?
I can easily stop building blackfin - and, if the intention is to
remove it, there is not much point in wasting resources building it any
anyway.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-07 12:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 5:37 [PATCH] dump_stack: convert generic dump_stack into a weak symbol Sergey Senozhatsky
2018-03-05 14:48 ` Petr Mladek
2018-03-06 2:50 ` Greentime Hu
2018-03-06 4:31 ` Sergey Senozhatsky
2018-03-06 5:34 ` Greentime Hu
2018-03-06 4:29 ` Sergey Senozhatsky
2018-03-06 12:43 ` Petr Mladek
2018-03-06 22:52 ` Stephen Rothwell
2018-03-06 13:27 ` Arnd Bergmann
2018-03-07 2:21 ` Sergey Senozhatsky
2018-03-07 8:46 ` Arnd Bergmann
2018-03-07 9:09 ` Petr Mladek
2018-03-07 9:44 ` Greentime Hu
2018-03-07 9:50 ` Arnd Bergmann
2018-03-07 10:40 ` Sergey Senozhatsky
2018-03-07 10:57 ` Arnd Bergmann
2018-03-07 11:48 ` Sergey Senozhatsky
2018-03-07 12:41 ` Stephen Rothwell [this message]
2018-03-07 12:48 ` Arnd Bergmann
2018-03-07 12:53 ` Stephen Rothwell
2018-03-07 12:58 ` Arnd Bergmann
2018-03-07 13:10 ` Stephen Rothwell
2018-03-07 13:40 ` Sergey Senozhatsky
2018-03-07 14:01 ` Sergey Senozhatsky
2018-03-09 9:50 ` Petr Mladek
2018-03-14 23:42 ` Steven Rostedt
2018-03-14 23:58 ` Stephen Rothwell
2018-03-07 8:49 ` Petr Mladek
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=20180307234142.1c7d2710@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=dyoung@redhat.com \
--cc=green.hu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@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 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).