From: Arnd Bergmann <arnd@arndb.de>
To: Mathieu Lacage <mathieu.lacage@gmail.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: patch submission process
Date: Wed, 28 Jul 2010 19:13:32 +0200 [thread overview]
Message-ID: <201007281913.32619.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTims43Q0k2bFX4nUvX40Fjhags5Oamw_R1RQOnuM@mail.gmail.com>
On Wednesday 28 July 2010, Mathieu Lacage wrote:
> One month ago, I followed arnd's suggestion and posted these two patches:
> http://marc.info/?l=linux-arch&m=127763437119458&w=2
> http://marc.info/?l=linux-arch&m=127719544028714&w=2
>
> and I would like to know if they were rejected because I screwed up
> something in the submission process or just forgotten or maybe merged
> in a tree I did not hear about.
>
> Is there a special process to follow to monitor the state of a patch
> submission ?
I'm sorry for being so unorganized on this, I should really have added
the patches into my git tree on git.kernel.org.
The best replacement for a process is to keep bugging the maintainer
until the patches show up in the linux-next kernel. I still have
you patch emails in my incoming mail folder.
Arnd
next prev parent reply other threads:[~2010-07-28 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 10:48 patch submission process Mathieu Lacage
2010-07-28 17:13 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-05 14:01 [PATCH] Add "Line In" input jack constants David Henningsson
2011-10-05 15:07 ` Mark Brown
2011-10-06 6:46 ` Patch submission process (was: [PATCH] Add "Line In" input jack constants) David Henningsson
2011-10-06 8:55 ` Patch submission process Clemens Ladisch
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=201007281913.32619.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=mathieu.lacage@gmail.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 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.