From: palmer@sifive.com (Palmer Dabbelt)
To: linux-riscv@lists.infradead.org
Subject: I've generated for-next
Date: Thu, 04 Oct 2018 17:25:18 -0700 (PDT) [thread overview]
Message-ID: <mhng-4f277f06-1d57-46e1-926b-a3bf06d6de13@palmer-si-x1c4> (raw)
There was a bug in my for-next generation script that was causing nothing to
get merged. I've fixed it and generated for-next, which contains all the
patches I hope to have for the 4.20 merge window. If I'm missing anything let
me know!
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@sifive.com>
To: linux-riscv@lists.infradead.org
Subject: I've generated for-next
Date: Thu, 04 Oct 2018 17:25:18 -0700 (PDT) [thread overview]
Message-ID: <mhng-4f277f06-1d57-46e1-926b-a3bf06d6de13@palmer-si-x1c4> (raw)
Message-ID: <20181005002518.YCfgID8t5XrTNSFyTJkWGDQZ3YjxA6Ln2v8-O-uZ0Qk@z> (raw)
There was a bug in my for-next generation script that was causing nothing to
get merged. I've fixed it and generated for-next, which contains all the
patches I hope to have for the 4.20 merge window. If I'm missing anything let
me know!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-10-05 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 0:25 Palmer Dabbelt [this message]
2018-10-05 0:25 ` I've generated for-next Palmer Dabbelt
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=mhng-4f277f06-1d57-46e1-926b-a3bf06d6de13@palmer-si-x1c4 \
--to=palmer@sifive.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.