All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@lst.de>, linux-arch <linux-arch@vger.kernel.org>
Subject: Re: kill <asm/segment.h> and improve nommu generic uaccess helpers
Date: Tue, 23 Apr 2019 20:32:32 +0200	[thread overview]
Message-ID: <20190423183232.GA26846@lst.de> (raw)
In-Reply-To: <CAK8P3a3D7F07kJAXp9yOh7FqEzL8rZeO5Xo9tGxpXFsibpShgg@mail.gmail.com>

On Tue, Apr 23, 2019 at 08:27:29PM +0200, Arnd Bergmann wrote:
> Should I pick this up into my asm-generic tree, or do you have another tree
> that this fits into? I might be on vacation during the entire merge window
> this time and don't have anything else for asm-generic, so I'd prefer if someone
> else could merge them.

Not sure where else it would fit.  It is in support for the RISC-V
nommu port, but that isn't ready for the merge window.

  reply	other threads:[~2019-04-23 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 16:38 kill <asm/segment.h> and improve nommu generic uaccess helpers Christoph Hellwig
2019-04-23 16:38 ` [PATCH 1/4] asm-generic: don't include <asm/segment.h> from <asm/uaccess.h> Christoph Hellwig
2019-04-23 16:38 ` [PATCH 2/4] arch: mostly remove <asm/segment.h> Christoph Hellwig
2019-04-23 16:38 ` [PATCH 3/4] asm-generic: provide entirely generic nommu uaccess Christoph Hellwig
2019-04-23 16:38 ` [PATCH 4/4] asm-generic: optimize generic uaccess for 8-byte loads and stores Christoph Hellwig
2019-04-23 18:27 ` kill <asm/segment.h> and improve nommu generic uaccess helpers Arnd Bergmann
2019-04-23 18:32   ` Christoph Hellwig [this message]
2019-04-23 18:41     ` Arnd Bergmann
2019-04-23 19:36       ` Christoph Hellwig
2019-04-23 19:58         ` Arnd Bergmann

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=20190423183232.GA26846@lst.de \
    --to=hch@lst.de \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.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.