From: Jani Nikula <jani.nikula@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Julia Lawall <julia.lawall@lip6.fr>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Maintainer's Summit Agenda Planning
Date: Wed, 11 Oct 2017 21:51:52 +0300 [thread overview]
Message-ID: <871sm9plfb.fsf@intel.com> (raw)
In-Reply-To: <1507568189.3100.29.camel@HansenPartnership.com>
On Mon, 09 Oct 2017, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Mon, 2017-10-09 at 18:49 +0200, Julia Lawall wrote:
>> Do you suggest one big patch, that goes to who? Or lots of little
>> patches that go out at once to the individual maintainers of the
>> affected code?
>
> I was actually thinking we validate the script and if there are no
> problems, apply it at -rc1 ... so effectively one big patch.
By -rc1 we (drm in general, drm/i915 in particular) will already have
accumulated easily 4-5 weeks' worth of commits for the *next* merge
window. Applying treewide stuff to Linus' tree at -rc1 forces a
backmerge and potentially conflicts galore I'm not particularly thrilled
about. I'd much rather see the patches to our driver come through our
tree, and we generally deal with them without a fuss.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-10-11 18:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 19:20 [Ksummit-discuss] Maintainer's Summit Agenda Planning Theodore Ts'o
2017-10-05 20:13 ` Rafael J. Wysocki
2017-10-05 21:55 ` Jiri Kosina
2017-10-06 14:59 ` Takashi Iwai
2017-10-06 15:27 ` James Bottomley
2017-10-06 16:26 ` Josh Poimboeuf
2017-10-06 16:32 ` Jonathan Corbet
2017-10-06 16:51 ` Josh Poimboeuf
2017-10-06 16:56 ` James Bottomley
2017-10-06 17:16 ` Josh Poimboeuf
2017-10-06 20:11 ` Linus Walleij
2017-10-09 8:13 ` Mark Brown
2017-10-09 15:54 ` Jiri Kosina
2017-10-09 16:37 ` James Bottomley
2017-10-09 16:47 ` Joe Perches
2017-10-09 16:49 ` Julia Lawall
2017-10-09 16:56 ` James Bottomley
2017-10-09 17:04 ` Joe Perches
2017-10-11 18:51 ` Jani Nikula [this message]
2017-10-12 10:03 ` Daniel Vetter
2017-10-16 14:12 ` James Bottomley
2017-10-16 14:25 ` Jani Nikula
2017-10-16 16:07 ` Joe Perches
2017-10-17 8:34 ` Jani Nikula
2017-10-18 1:27 ` Joe Perches
2017-10-18 10:41 ` Jani Nikula
2017-10-16 18:52 ` Mark Brown
2017-10-10 8:53 ` Jiri Kosina
2017-10-24 23:03 ` Kees Cook
2017-10-24 23:41 ` Joe Perches
2017-10-25 0:54 ` Kees Cook
2017-10-25 4:21 ` Julia Lawall
2017-10-25 4:29 ` Joe Perches
2017-10-25 4:36 ` Julia Lawall
2017-10-25 6:05 ` Martin K. Petersen
2017-10-25 6:55 ` Kees Cook
2017-10-25 7:34 ` Martin K. Petersen
2017-10-25 6:45 ` Frank Rowand
2017-10-25 7:56 ` Mark Brown
2017-10-25 9:39 ` Laurent Pinchart
2017-10-31 19:19 ` Rob Herring
2017-10-31 19:28 ` Kees Cook
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=871sm9plfb.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=julia.lawall@lip6.fr \
--cc=ksummit-discuss@lists.linuxfoundation.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 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.