From: Richard Weinberger <richard@nod.at>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [GIT PULL] UBI/UBIFS updates for 4.15-rc1
Date: Fri, 24 Nov 2017 10:46:37 +0100 [thread overview]
Message-ID: <4300266.OpBMifGIty@blindfold> (raw)
In-Reply-To: <CA+55aFw-NJXZ9O9JJigeTdK2V6y7zpQfmE3rmsB1Zi=8kMJuZA@mail.gmail.com>
Linus,
Am Freitag, 24. November 2017, 04:41:37 CET schrieb Linus Torvalds:
> On Thu, Nov 23, 2017 at 4:37 AM, Richard Weinberger <richard@nod.at> wrote:
> > git://git.infradead.org/linux-ubifs.git tags/upstream-4.15-rc1
>
> Similarly to the arch/um case, none of this seems to have been in
> linux-next, and is sent late in the merge window, so I'm skipping it.
It is since next-20171120 in linux-next.
I'm sorry for being late, will do a better job next time.
If you don't mind I'll send you a PR with bug fixes for 4.15-rc2.
Same for UML.
Thanks,
//richard
parent reply other threads:[~2017-11-24 9:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+55aFw-NJXZ9O9JJigeTdK2V6y7zpQfmE3rmsB1Zi=8kMJuZA@mail.gmail.com>]
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=4300266.OpBMifGIty@blindfold \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).