All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel
Date: Fri, 14 Jul 2017 18:51:42 +0300	[thread overview]
Message-ID: <20170714155142.GF1528@mtr-leonro.local> (raw)
In-Reply-To: <20170714150550.ubtkwmd3wcx554m6@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

On Fri, Jul 14, 2017 at 04:05:50PM +0100, Mark Brown wrote:
> On Fri, Jul 14, 2017 at 04:10:57PM +0200, Andrew Lunn wrote:
> > > The difference in maintainers style between netdev and RDMA causes to have long queue
> > > (100+) of patches posted to the ML [2], which are not cross-checked in various CIs.
>
> > It is possible to get 0-day to run against any arbitrary git tree, if
> > you ask nicely. If same is true for the kernel-ci project. So if you
> > are willing to do the merge work, you can get it tested.
>
> Trees can be added to kernelci, yes.  Another approach would be to work
> out a workflow with the upstreams that makes this better, if they'd take
> pull requests for example.

Isn't the goal of this topic in maintainers summit? Improving workflows :)

So, my way to overcome my issues was to add "parallel" tree and to stop
crying about "long queues".

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-07-14 15:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 23:01 [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel Kees Cook
2017-06-29 13:39 ` Christoph Hellwig
2017-06-30 13:02   ` Daniel Vetter
2017-06-29 16:36 ` James Bottomley
2017-06-29 16:51   ` Kees Cook
2017-06-29 17:42     ` James Bottomley
2017-06-29 17:52       ` Kees Cook
2017-06-29 18:20         ` Luis R. Rodriguez
2017-06-29 19:07           ` Linus Torvalds
2017-06-29 20:16           ` Kees Cook
2017-06-29 20:27             ` Stephen Rothwell
2017-07-14  4:04               ` Leon Romanovsky
2017-07-14  9:54                 ` Greg KH
2017-07-14 10:29                   ` Leon Romanovsky
2017-07-14 14:10                     ` Andrew Lunn
2017-07-14 15:05                       ` Mark Brown
2017-07-14 15:51                         ` Leon Romanovsky [this message]
2017-07-14 16:20                           ` Mark Brown
2017-07-14 15:35                       ` Leon Romanovsky
2017-07-14 15:43                         ` James Bottomley
2017-07-14 16:08                           ` Leon Romanovsky
2017-07-14 16:18                         ` Andrew Lunn
2017-07-14 16:28                           ` Bart Van Assche

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=20170714155142.GF1528@mtr-leonro.local \
    --to=leon@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=broonie@kernel.org \
    --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.