All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jesper Nilsson <jespern@axis.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Michal Simek <monstr@monstr.eu>, Andi Kleen <ak@linux.intel.com>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-cris-kernel@axis.com, Petr Mladek <pmladek@suse.com>,
	Peter Zijlstra <peterz@infradead.org>,
	adi-buildroot-devel@lists.sourceforge.net,
	Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesper Nilsson <jesper@jni.nu>, Greentime Hu <green.hu@gmail.com>,
	Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vincent Chen <deanbo422@gmail.com>,
	Dave Young <dyoung@redhat.com>
Subject: Re: [GIT PULL] CRIS: Drop support for the CRIS-port
Date: Tue, 13 Mar 2018 10:26:38 +0100	[thread overview]
Message-ID: <20180313092638.GC17177@axis.com> (raw)
In-Reply-To: <CAK8P3a2LRyHmQ1=bFwrW9a3RR53W0CiiakNTg2823utAnVpBmQ@mail.gmail.com>

On Mon, Mar 12, 2018 at 09:21:25PM +0100, Arnd Bergmann wrote:
> On Sun, Mar 11, 2018 at 12:05 PM, Jesper Nilsson
> <jesper.nilsson@axis.com> wrote:
> > Hi Arnd,
> >
> > As promised, pull the below tag for the removal of the CRIS-port.
> > There are still a few references to the CRIS port left, and they
> > can be grouped into two categories:
> >
> > - Examples or references to the CRIS port as provenance.
> >         These I believe can be left as is.
> >
> > - The workarounds for CRIS not having "unpacked" structs.
> >         When I looked at it 10 years ago, CRIS was the only port
> >         that needed explicit alignment of some structs,
> >         due to pointers being valid at any byte offset in CRIS,
> >         which would wreak havoc with code that assumed that the
> >         lower bits of a pointer are free to use as flags.
> >         I'm leaving these in until we can say that no newer
> >         port has the same problem.
> >
> > Best regards,
> 
> Hi Jesper,
> 
> Thanks for the patch! I had done a slightly different approach, but
> am merging your changes into my tree now. I already have separate
> patches for each driver subsystem, so I'll keep my versions, having
> already made sure that your changes were identical.
> 
> For Documentation/features and the Kconfig files that have lists
> of architectures, I also have separate patches that do the changes
> for all architectures, to avoid touching those files (up to) eight times
> for one trivial change each. I could redo those, but since your patch
> conflicts with David Howell's patch for mn10300, it's easier to keep
> what I already have.
> 
> This leaves basically the removal of arch/cris along with the MAINTAINER
> file update. I'm keeping the patch I did, but change the author and
> changelog text to what you sent, with my Signed-off-by and a list
> of my modifications) added below.
> 
> Hope that works for you.

Yeah, no problem, and thanks.

>      Arnd

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

      reply	other threads:[~2018-03-13  9:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 14:09 CRIS port status, was: [PATCH] dump_stack: convert generic dump_stack into a weak symbol Arnd Bergmann
2018-03-07 15:01 ` Michal Simek
2018-03-07 16:05   ` Arnd Bergmann
2018-03-08 15:51 ` Jesper Nilsson
2018-03-11 11:05   ` [GIT PULL] CRIS: Drop support for the CRIS-port Jesper Nilsson
2018-03-11 12:26     ` Mikael Starvik
2018-03-11 14:13     ` Stephen Rothwell
2018-03-11 20:00       ` Jesper Nilsson
2018-03-11 23:12         ` Stephen Rothwell
2018-03-12 20:21     ` Arnd Bergmann
2018-03-13  9:26       ` Jesper Nilsson [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=20180313092638.GC17177@axis.com \
    --to=jesper.nilsson@axis.com \
    --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=jesper@jni.nu \
    --cc=jespern@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --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 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.