linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <Tudor.Ambarus@microchip.com>,
	Richard Weinberger <richard@nod.at>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mtd@lists.infradead.org,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [GIT PULL] mtd: Fixes for v5.5-rc6
Date: Sat, 11 Jan 2020 09:50:04 -0500	[thread overview]
Message-ID: <20200111145004.htnpdf6oaiksryxz@chatter.i7.local> (raw)
In-Reply-To: <CAHk-=whdsFSX0gTOiNkTANONgHHVY+8jUd1DmY2SJpdNOq5xJw@mail.gmail.com>

On Fri, Jan 10, 2020 at 12:38:37PM -0800, Linus Torvalds wrote:
> On Fri, Jan 10, 2020 at 12:31 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Konstantin, can you see what's wrong?
> 
> It's not just Miquel's. The sound, thermal, and power management fixes
> pulls seem to also be lacking pr-tracker-bot responses.
> 
> But Jens got one for block - but that went to the block mailing list,
> not lkml. So maybe it's specific to lkml itself.
> 
> Maybe things are just slow, and I have gotten used to the
> almost-instant responses when I do a "git push" to publish my pulls.

Sorry about that. The public-inbox repository for LKML automatically 
rolled over to start a new epoch (from 7.git to 8.git). This only 
happens once about every 6-9 months and is such a rare occurrence that 
it's hard to properly catch all potential gotchas.

Things should be unstuck now, and at least this particular bug is fixed 
-- hopefully it'll be smooth and automatic the next time the epoch rolls 
over to 9.git.

Regards,
-K

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-01-11 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 14:42 [GIT PULL] mtd: Fixes for v5.5-rc6 Miquel Raynal
2020-01-10 20:31 ` Linus Torvalds
2020-01-10 20:38   ` Linus Torvalds
2020-01-11 14:50     ` Konstantin Ryabitsev [this message]
2020-01-13  8:02       ` Geert Uytterhoeven
2020-01-13 20:52         ` Konstantin Ryabitsev
2020-01-11 14:45 ` pr-tracker-bot

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=20200111145004.htnpdf6oaiksryxz@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.org \
    --cc=vigneshr@ti.com \
    /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).