From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: rtl8723au: Fix brace coding style issues reported by checkpatch
Date: Wed, 29 Oct 2014 20:04:06 -0400 [thread overview]
Message-ID: <54518076.6050600@gmail.com> (raw)
In-Reply-To: <CAFB9KM0pr2yk-mTE924uXpTLbeAK1MDsiUuMd-bRn8y_B076bg@mail.gmail.com>
I don't mind waiting. I am just honestly trying to improve my rep here and actually(hopefully) get a job
doing this full time.
Cheers Nick
On 14-10-29 04:45 AM, Scott Lovenberg wrote:
> On Wed, Oct 29, 2014 at 1:48 AM, Sudip Mukherjee
> <sudipm.mukherjee@gmail.com> wrote:
>> On Wed, Oct 29, 2014 at 11:38 AM, Scott Lovenberg
>> <scott.lovenberg@gmail.com> wrote:
>>> On Wed, Oct 29, 2014 at 12:05 AM, Sudip Mukherjee
>>> <sudipm.mukherjee@gmail.com> wrote:
>>>>
>>>> On Wed, Oct 29, 2014 at 7:31 AM, nick <xerofoify@gmail.com> wrote:
>>>>> Greg,
>>>>> That's fine, I was wondering how long Greg KH takes to get around to picking this up as he is very busy with
>>>>> other kernel work.
>>>>
>>>> it might take a long long time. i think he is very busy now. I have
>>>> not seen his replies to patches in the kernel list for atleast last 3
>>>> weeks.
>>>>
>>> [snip]
>>>>
>>>> _______________________________________________
>>>> Kernelnewbies mailing list
>>>> Kernelnewbies at kernelnewbies.org
>>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>>>
>>>
>>> Nah. Greg KH is a robot. I'm firmly convinced that man doesn't
>>> sleep. If I didn't know better, I'd think he's a Cylon.
>> well said.
>>
>>> On a serious note; realistically, a two week window isn't unheard of
>>> for getting your patches to mainline. So long as you're not trying to
>>
>> mine is three weeks going on now. somehow i have managed to send my
>> patches just at the beginning of the merge window. :(
>> yesterday i saw Greg K-H releasing the stable patches , so i guess now
>> he will be seeing the pending staging patches.
>
> It also depends on how many hops you are to the maintainer and how
> heavy their workload is. Sometimes you can directly submit to them,
> other times your patches will be passed through three trees before
> they see mainline. It all depends on what you're working on and who's
> in your "circle".
>
next prev parent reply other threads:[~2014-10-30 0:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 19:52 [PATCH] staging: rtl8723au: Fix brace coding style issues reported by checkpatch Nicholas Krause
2014-10-28 8:24 ` Jeff Kirsher
2014-10-28 16:50 ` Greg Freemyer
2014-10-28 17:39 ` Greg Donald
2014-10-28 17:53 ` Nick Krause
2014-10-28 18:06 ` Greg Donald
2014-10-28 19:52 ` nick
2014-10-28 21:31 ` Greg Donald
2014-10-29 1:49 ` nick
2014-10-29 1:58 ` Jeff Kirsher
2014-10-29 2:01 ` nick
2014-10-29 2:04 ` Jeff Kirsher
2014-10-29 2:06 ` nick
2014-10-29 5:05 ` Sudip Mukherjee
2014-10-29 6:08 ` Scott Lovenberg
2014-10-29 6:48 ` Sudip Mukherjee
2014-10-29 8:45 ` Scott Lovenberg
2014-10-30 0:04 ` nick [this message]
2014-10-30 4:21 ` Sudip Mukherjee
2014-10-30 10:14 ` nick
2014-10-28 18:07 ` Jeff Haran
2014-10-28 18:20 ` Mandeep Sandhu
2014-10-28 20:59 ` Greg Donald
2014-10-28 18:42 ` Valdis.Kletnieks at vt.edu
2014-10-28 19:04 ` John de la Garza
2014-10-28 20:55 ` Greg Donald
2014-10-28 21:33 ` John de la Garza
-- strict thread matches above, loose matches on Subject: below --
2014-10-28 13:27 Nicholas Krause
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=54518076.6050600@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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.