public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Joe Perches <joe@perches.com>
Cc: linuxppc-dev@lists.ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Sasha Levin <sasha.levin@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hashtable: add hash_for_each_possible_rcu_notrace()
Date: Tue, 23 Jul 2013 12:43:18 +1000	[thread overview]
Message-ID: <51EDEDC6.2040007@ozlabs.ru> (raw)
In-Reply-To: <1374547276.8308.12.camel@joe-AO722>

On 07/23/2013 12:41 PM, Joe Perches wrote:
> On Tue, 2013-07-23 at 12:28 +1000, Alexey Kardashevskiy wrote:
>> Anyone, ping. Is it good, bad, ugly (ack/nack)? Thanks!
>>
>> Is there any "trivial patches" list? Could not find it on vger.
> 
> Jiri Kosina has trivial@kernel.org
> 
> Also, there's kernel-janitors
> 
> http://vger.kernel.org/vger-lists.html#kernel-janitors
> http://kernelnewbies.org/KernelJanitors
> 
> MAINTAINERS has an entry:
> 
> TRIVIAL PATCHES
> M:	Jiri Kosina <trivial@kernel.org>
> T:	git git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git
> S:	Maintained
> K:	^Subject:.*(?i)trivial


Cool, thanks! But is that patch really trivial? :)


-- 
Alexey

  reply	other threads:[~2013-07-23  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-06  4:16 [PATCH] hashtable: add hash_for_each_possible_rcu_notrace() Alexey Kardashevskiy
2013-07-15 10:04 ` Alexey Kardashevskiy
2013-07-23  2:28   ` Alexey Kardashevskiy
2013-07-23  2:41     ` Joe Perches
2013-07-23  2:43       ` Alexey Kardashevskiy [this message]
2013-07-23  2:53         ` Joe Perches
2013-07-23  7:52           ` Benjamin Herrenschmidt

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=51EDEDC6.2040007@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=sasha.levin@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox