All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kukkonen <m.kukkonen@samsung.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/14] JANITOR: Remove include/linux/sys.h
Date: Wed, 30 Oct 2013 11:29:31 +0000	[thread overview]
Message-ID: <20131030112931.GD26766@nbf-011.seri.co.uk> (raw)
In-Reply-To: <20131029095347.GA12832@nbf-011.seri.co.uk>

On Wed, Oct 30, 2013 at 11:03:57AM +0000, Julia Lawall wrote:
> On Wed, 30 Oct 2013, Mika Kukkonen wrote:
> 
> > On Tue, Oct 29, 2013 at 01:36:09PM +0000, Dan Carpenter wrote:
> > >
> > > Kernel Janitors doesn't have an a patch tree.  In theory these could all
> > > go through trivial@kernel.org or they could go to the subsystem
> > > maintainers.  You pretty much have broken it up by subsystem already.
> >
> > Yes, but I chickened out and did not want to CC 14 subsystem maintainers. ;-)
> 
> I've deleted the mail with the patches, but if it would be useful for the
> maintainers to see the patches, you should send them to them.  That is,
> send each patch to the people indicated by get_maintainers.

Yeah, I'll probably do that, but I got bunch other janitorial stuff(*) in pipeline,
so I will probably delay this to next merge window as this is in no way urgent.

--MiKu

(*) Basically I am trying to make "make W=1" usefull, I just happened to stumble
    upon this <linux/sys.h> while working on that.


      parent reply	other threads:[~2013-10-30 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29  9:53 [PATCH 0/14] JANITOR: Remove include/linux/sys.h Mika Kukkonen
2013-10-29 13:36 ` Dan Carpenter
2013-10-30 10:59 ` Mika Kukkonen
2013-10-30 11:03 ` Julia Lawall
2013-10-30 11:29 ` Mika Kukkonen [this message]

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=20131030112931.GD26766@nbf-011.seri.co.uk \
    --to=m.kukkonen@samsung.com \
    --cc=kernel-janitors@vger.kernel.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.