From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PULL REQUEST] i2c for v5.8
Date: Sat, 25 Jul 2020 16:46:03 +0200 [thread overview]
Message-ID: <20200725144603.GA4013@kunai> (raw)
In-Reply-To: <CAHk-=wjaHZKQnOuGLWukvMrTmDrDd6iyiq5toQumB2uX1nR9Xw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Linus,
> Do you have a lot of pending fixes? Because things _seem_ fairly quiet
> for this release, and right now it doesn't seem to make much sense to
> delay 5.8.
No, it is not about fixes. I have one fix pending and I am quite sure we
make it for 5.8.
It would simply give me one more week to get some not-so-complex I2C
driver updates into 5.9 which I couldn't apply before because of my
holidays. With the next merge window this soon, I can now choose to let
people wait 3 more months or to put some stress on my side (bye bye
holiday relaxation).
So, I wondered if maybe more maintainers would be in a similar siuation
and we could get an extra week to catch up (I know this is not a
technical reason).
Anyhow, given your response, this seems not the case.
Kind regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-25 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 19:27 [PULL REQUEST] i2c for v5.8 Wolfram Sang
2020-07-24 20:43 ` Linus Torvalds
2020-07-25 14:46 ` Wolfram Sang [this message]
2020-07-24 21:40 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-05-19 6:36 Wolfram Sang
2020-05-19 6:40 ` Wolfram Sang
2020-05-19 19:00 ` 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=20200725144603.GA4013@kunai \
--to=wsa@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox