From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] UBIFS fixes for 4.19-rc4
Date: Fri, 21 Sep 2018 16:08:10 +0200 [thread overview]
Message-ID: <20180921140810.GA15210@kroah.com> (raw)
In-Reply-To: <1614017.BCjLPTCWnn@blindfold>
On Fri, Sep 21, 2018 at 04:01:33PM +0200, Richard Weinberger wrote:
> Am Freitag, 21. September 2018, 15:53:42 CEST schrieb Greg KH:
> > On Fri, Sep 21, 2018 at 11:33:15AM +0200, Richard Weinberger wrote:
> > > Greg,
> > >
> > > The following changes since commit ae596de1a0c8c2c924dc99d23c026259372ab234:
> > >
> > > Compiler Attributes: naked can be shared (2018-09-20 15:23:58 +0200)
> >
> > Wow, bold move, new patches with less than 24 hours in your tree. That
> > means linux-next didn't see them :(
> >
> > > are available in the Git repository at:
> > >
> > > git://git.infradead.org/linux-ubifs.git tags/upstream-4.19-rc4
> >
> > Now pulled, but really, don't you think that they should at least go
> > through 0-day first? Maybe no one runs ubifs on mainline kernels...
>
> Huh? I checked this morning next-20180921 and saw all patches.
Ah, ok, must have snuck in, I assumed that less than 24 hours was pretty
fast...
next prev parent reply other threads:[~2018-09-21 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 9:33 [GIT PULL] UBIFS fixes for 4.19-rc4 Richard Weinberger
2018-09-21 13:53 ` Greg KH
2018-09-21 14:01 ` Richard Weinberger
2018-09-21 14:08 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-24 7:11 Peter Rosin
2018-09-24 7:19 ` Greg KH
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=20180921140810.GA15210@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.