linux-kernel - Re: [PATCH] IB/ehca: use kthread_create_on

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZOPZJs6KpcRTc2HH0rEiParY=ZQUkXZmoUzh2OwZw9+rDjsQ@mail.gmail.com>
Date:	Thu, 9 Feb 2012 00:28:46 +0200
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	Roland Dreier <roland@...nel.org>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	Sean Hefty <sean.hefty@...el.com>, linux-rdma@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] IB/ehca: use kthread_create_on_node

On Wed, Feb 8, 2012 at 11:35 PM, Roland Dreier <roland@...nel.org> wrote:
> On Wed, Feb 8, 2012 at 1:26 PM, Or Gerlitz <or.gerlitz@...il.com> wrote:

>> [...] This means that the window of time when features are actually accepted
>> into your tree is kind of very limited. Would it be possible to
>> maintain two branches: for-next and (say) rc-fixes, such that
>> practically patches are reviewed/accepted to for-next at almost all times?

>> BTW I see that networking and scsi maintainers use two trees (net/net-next)
>> and (scsi-misc/scsi-rc-fixes), maybe it would be eaiser for you go this way?

> It's not really an issue of not having a tree to put things into.  It's
> more that the window when I actually review major things is not
> as big as perhaps it should be.

> So I generally try to get fixes in expeditiously because they're
> easy to deal with, whereas I only dedicate time to merging bigger
> things when I feel the pressure of the impending merge window.

but bigger things need bigger time to deal with... but even before we
address that -

> I do usually have some small patches that are fine for the next window
> but which I have only marked "to apply" in my mailbox, which it
> might be a good idea to apply sooner so they get more -next tree coverage.

Yep, having a branch where patches you accept are applied sooner
rather then later,
will be a little but surely nice && important step in the right
direction... it would be great to have this, could you make that
happen?

Also, to except for patches which you reviewed and willing to accept,
it happens that Sean Hefty who is also a maintainer, reviews patches
and provides his reviewed-by signature. I would say such patches could
(should) go to that branch as well and not wait to the pressure of the
impending merge window.

How does all this sound?

Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/