From: Jason Cooper <jason@lakedaemon.net>
To: Jake Edge <jake@lwn.net>
Cc: Anton Saraev <antonysaraev@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH v2 1/1] staging/skein: rename files and clean up directory structure
Date: Sun, 18 May 2014 19:15:51 -0400 [thread overview]
Message-ID: <20140518231551.GZ27822@titan.lakedaemon.net> (raw)
In-Reply-To: <20140518170450.272a1381@chukar.edge2.net>
On Sun, May 18, 2014 at 05:04:50PM -0600, Jake Edge wrote:
> On Sun, 18 May 2014 18:52:31 -0400 Jason Cooper wrote:
>
> > Jake, would you mind dropping this patch and perhaps assisting me with
> > reviewing Anton's series? I'll have him resend it as-is and we can go
> > from there.
>
> No, that's fine. Guess I'll put my patches to clean up some other
> stuff (function names, etc.) on hold and see how far Anton got ...
>
> fwiw, I did look at the lists to see if someone had already been
> working on this stuff, which is why it is such a good idea make sure the
> patches get posted publicly ...
Yes, I agree. It was a perfect storm of "Are my first patches good
enough for the mailinglist?", "Hey, Jason, thanks for taking on
drivers/irqchip", and "We need to get everything in before -rc6 for the
mvebu/arm-soc cutoff before the merge window". Apparently, I'm not very
good at juggling three separate rushes at once. :)
Anton has the submission process down now, so from here on out he'll
just send them to the list.
Thanks for your understanding.
thx,
Jason.
next prev parent reply other threads:[~2014-05-18 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 18:56 Jake Edge
2014-05-18 22:52 ` Jason Cooper
2014-05-18 23:04 ` Jake Edge
2014-05-18 23:15 ` Jason Cooper [this message]
2014-05-19 22:22 ` Greg Kroah-Hartman
2014-05-19 23:48 ` [PATCH v3 " Jake Edge
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=20140518231551.GZ27822@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=antonysaraev@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jake@lwn.net \
--cc=joe@perches.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®