From: Sasha Levin <sashal@kernel.org>
To: Richard Weinberger <richard@nod.at>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
martin.kepplinger@ginzinger.com, Stable <stable@vger.kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
linux-mtd@lists.infradead.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Juergen <juergen.lachmann@harman.com>
Subject: Re: [PATCH] ubi: fastmap: Check each mapping only once
Date: Sun, 2 Dec 2018 10:32:44 -0500 [thread overview]
Message-ID: <20181202153244.GJ221015@sasha-vm> (raw)
In-Reply-To: <1678636.EYQpd7BODG@blindfold>
On Sun, Dec 02, 2018 at 04:02:47PM +0100, Richard Weinberger wrote:
>Sasha,
>
>Am Sonntag, 2. Dezember 2018, 15:35:43 CET schrieb Sasha Levin:
>> On Sun, Dec 02, 2018 at 11:50:33AM +0000, Sudip Mukherjee wrote:
>> >> > Now queued up for 4.14.y, thanks.
>> >>
>> >> can you *please* slow a little down?
>> >
>> >True. It will really help if you can have some sort of fixed schedule
>> >for stable release, like maybe stablerc is ready on Thursday or Friday
>> >and release the stable on Monday. Having a weekend in stablerc will be
>> >helpful for people like me who only get the time in weekends for
>> >upstream or stable kernel.
>>
>> Any sort of schedule will never work for everyone (for example, if it's
>> part of your paid job - you don't necessarily want to review stuff over
>> the weekend).
>
>a schedule is not needed, but please give maintainers at least a chance
>to react on stable inclusion request.
>In this case Martin asked for inclusion on Monday and the patch was applied
>two days later.
>
>As you noted not everyone works full time on the kernel and gets paid for that.
>So it might take a few days to react and review such a request.
Yes, that's fair, I wasn't arguing against that.
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-12-02 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 10:38 [PATCH] ubi: fastmap: Check each mapping only once Martin Kepplinger
2018-11-29 8:09 ` Greg KH
2018-12-02 8:51 ` Richard Weinberger
2018-12-02 11:50 ` Sudip Mukherjee
2018-12-02 14:35 ` Sasha Levin
2018-12-02 15:02 ` Richard Weinberger
2018-12-02 15:32 ` Sasha Levin [this message]
2018-12-04 7:39 ` Martin Kepplinger
2018-12-04 7:39 ` Martin Kepplinger
2018-12-04 7:41 ` Greg Kroah-Hartman
2018-12-02 15:04 ` Sudip Mukherjee
2018-12-06 11:09 ` 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=20181202153244.GJ221015@sasha-vm \
--to=sashal@kernel.org \
--cc=dedekind1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=juergen.lachmann@harman.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.kepplinger@ginzinger.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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 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.