From: David Howells <dhowells@redhat.com>
To: Akshay Joshi <me@akshayjoshi.com>
Cc: dhowells@redhat.com, Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
James Morris <jmorris@namei.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] Kernel: fix spaces with respect to the coding style in sys.c.
Date: Tue, 07 Jun 2011 15:54:18 +0100 [thread overview]
Message-ID: <26045.1307458458@redhat.com> (raw)
In-Reply-To: <BANLkTikkBgYx2qPVEXyyAbr0Vsi=_vORqA@mail.gmail.com>
Akshay Joshi <me@akshayjoshi.com> wrote:
> I am very new to submitting patches to the kernel. Do I just modify the
> patch file and add an Acked-by line to the patch notes or do I have to do
> something else?
If you've got a whole bunch of acks, then it may make sense to resubmit your
patches with them included and a note in patch 0 saying that that's all that
you've done. This is one of the downsides of this process - it doesn't cope
so easily with additions of this type.
David
next prev parent reply other threads:[~2011-06-07 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 10:39 [PATCH 2/7] Kernel: space and brace fixes for user_namespace.c Akshay Joshi
2011-06-07 10:39 ` [PATCH 3/7] Kernel: Fix trailing whitespace in user.c Akshay Joshi
2011-06-07 10:39 ` [PATCH 4/7] Kernel: convert leading spaces to tabs in uid16.c Akshay Joshi
2011-06-07 15:43 ` Akshay Joshi
2011-06-07 10:39 ` [PATCH 5/7] Kernel: add spaces where required by the coding style in acct.c Akshay Joshi
2011-06-07 10:39 ` [PATCH 6/7] Kernel: fix spaces with respect to the coding style in sys.c Akshay Joshi
2011-06-07 13:30 ` David Howells
[not found] ` <BANLkTikkBgYx2qPVEXyyAbr0Vsi=_vORqA@mail.gmail.com>
2011-06-07 14:54 ` David Howells [this message]
2011-06-07 15:44 ` Akshay Joshi
2011-06-07 10:39 ` [PATCH 7/7] Kernel: style fixes to spaces for sysctl.c Akshay Joshi
2011-06-07 15:41 ` [PATCH 3/7] Kernel: Fix trailing whitespace in user.c Akshay Joshi
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=26045.1307458458@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jmorris@namei.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=me@akshayjoshi.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