All of lore.kernel.org
 help / color / mirror / Atom feed
From: david.abdurachmanov@gmail.com (David Abdurachmanov)
To: linux-riscv@lists.infradead.org
Subject: [PULL RFC] RISC-V Patches for the 4.20 Merge Window, Part 1
Date: Tue, 23 Oct 2018 10:20:28 +0200	[thread overview]
Message-ID: <CAEn-LTqbEmWovu4t7Rs4C211+GRRU4V3B=+WmW0SOhX_b8db5Q@mail.gmail.com> (raw)
In-Reply-To: <mhng-737b95bd-3a5b-44c7-ac14-3af4bbcca32e@palmer-si-x1c4>

On Tue, Oct 23, 2018 at 3:20 AM Palmer Dabbelt <palmer@sifive.com> wrote:

> I'm pretty sure this is our largest patch set since the original kernel
> contribution, and it's certainly the one with the most contributors.
> While I don't have anything else I know I'm going to submit for the
> merge window, I would be somewhat surprised if I didn't screw anything
> up.

Hi Palmer,

Do you plan to land wip-seccomp in 4.20?

It was mentioned back in August:
http://lists.infradead.org/pipermail/linux-riscv/2018-August/001182.html

david

WARNING: multiple messages have this Message-ID (diff)
From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PULL RFC] RISC-V Patches for the 4.20 Merge Window, Part 1
Date: Tue, 23 Oct 2018 10:20:28 +0200	[thread overview]
Message-ID: <CAEn-LTqbEmWovu4t7Rs4C211+GRRU4V3B=+WmW0SOhX_b8db5Q@mail.gmail.com> (raw)
Message-ID: <20181023082028.yo8UaMXJAKA0BDbmlJYRryxs-79n8-IbmaPMA3tcoQI@z> (raw)
In-Reply-To: <mhng-737b95bd-3a5b-44c7-ac14-3af4bbcca32e@palmer-si-x1c4>

On Tue, Oct 23, 2018 at 3:20 AM Palmer Dabbelt <palmer@sifive.com> wrote:

> I'm pretty sure this is our largest patch set since the original kernel
> contribution, and it's certainly the one with the most contributors.
> While I don't have anything else I know I'm going to submit for the
> merge window, I would be somewhat surprised if I didn't screw anything
> up.

Hi Palmer,

Do you plan to land wip-seccomp in 4.20?

It was mentioned back in August:
http://lists.infradead.org/pipermail/linux-riscv/2018-August/001182.html

david

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2018-10-23  8:20 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  1:20 [PULL RFC] RISC-V Patches for the 4.20 Merge Window, Part 1 Palmer Dabbelt
2018-10-23  1:20 ` Palmer Dabbelt
2018-10-23  8:20 ` David Abdurachmanov [this message]
2018-10-23  8:20   ` David Abdurachmanov
2018-10-24 20:40   ` [PATCH 0/2] RISC-V: Add support for SECCOMP Palmer Dabbelt
2018-10-24 20:40     ` Palmer Dabbelt
2018-10-24 20:40     ` Palmer Dabbelt
2018-10-24 20:40     ` Palmer Dabbelt
2018-10-24 20:40     ` [PATCH 1/2] Move EM_RISCV into elf-em.h Palmer Dabbelt
2018-10-24 20:40       ` Palmer Dabbelt
2018-10-24 20:40       ` Palmer Dabbelt
2018-10-24 20:40       ` Palmer Dabbelt
2018-10-24 21:26       ` Kees Cook
2018-10-24 21:26         ` Kees Cook
2018-10-24 21:26         ` Kees Cook
2018-10-25  3:04       ` Paul Walmsley
2018-10-25  3:04         ` Paul Walmsley
2018-10-27  7:46       ` Christoph Hellwig
2018-10-27  7:46         ` Christoph Hellwig
2018-10-27  7:46         ` Christoph Hellwig
2018-10-27  7:46         ` Christoph Hellwig
2018-10-27  9:10         ` David Abdurachmanov
2018-10-27  9:10           ` David Abdurachmanov
2018-10-27  9:10           ` David Abdurachmanov
2018-10-24 20:40     ` [PATCH 2/2] RISC-V: Add support for SECCOMP Palmer Dabbelt
2018-10-24 20:40       ` Palmer Dabbelt
2018-10-24 20:40       ` Palmer Dabbelt
2018-10-24 20:40       ` Palmer Dabbelt
2018-10-24 21:42       ` Kees Cook
2018-10-24 21:42         ` Kees Cook
2018-10-24 21:42         ` Kees Cook
2018-10-24 21:42         ` Kees Cook
2018-10-24 22:34         ` Kees Cook
2018-10-24 22:34           ` Kees Cook
2018-10-24 22:34           ` Kees Cook
2018-10-25 21:02         ` Andy Lutomirski
2018-10-25 21:02           ` Andy Lutomirski
2018-10-25 21:02           ` Andy Lutomirski
2018-10-27  6:07           ` Palmer Dabbelt
2018-10-27  6:07             ` Palmer Dabbelt
2018-10-27  6:07             ` Palmer Dabbelt
2018-10-25 18:31       ` David Abdurachmanov
2018-10-25 18:31         ` David Abdurachmanov
2018-10-25 18:31         ` David Abdurachmanov
2018-10-25 20:36         ` Paul Moore
2018-10-25 20:36           ` Paul Moore
2018-10-25 20:36           ` Paul Moore
2018-10-28 11:07           ` David Abdurachmanov
2018-10-28 11:07             ` David Abdurachmanov
2018-10-28 11:07             ` David Abdurachmanov
2018-10-29 20:27             ` Palmer Dabbelt
2018-10-29 20:27               ` Palmer Dabbelt
2018-10-29 20:27               ` Palmer Dabbelt
2018-11-02 13:32               ` David Abdurachmanov
2018-11-02 13:32                 ` David Abdurachmanov
2018-11-02 13:32                 ` David Abdurachmanov
2018-11-02 15:51                 ` Kees Cook
2018-11-02 15:51                   ` Kees Cook
2018-11-02 15:51                   ` Kees Cook
2018-10-27  6:07         ` Palmer Dabbelt
2018-10-27  6:07           ` Palmer Dabbelt
2018-10-27  6:07           ` Palmer Dabbelt
2018-10-27  6:07           ` Palmer Dabbelt
2018-10-27  7:55       ` Christoph Hellwig
2018-10-27  7:55         ` Christoph Hellwig
2018-10-27  7:55         ` Christoph Hellwig
2018-10-27  7:55         ` Christoph Hellwig

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='CAEn-LTqbEmWovu4t7Rs4C211+GRRU4V3B=+WmW0SOhX_b8db5Q@mail.gmail.com' \
    --to=david.abdurachmanov@gmail.com \
    --cc=linux-riscv@lists.infradead.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.