From: Joerg Roedel <joro@8bytes.org>
To: re.emese@gmail.com
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
jens.axboe@oracle.com
Subject: Re: [PATCH 0/3] Constify struct block_device_operations for 2.6.32-git-053fe57ac v2
Date: Mon, 14 Dec 2009 11:10:09 +0100 [thread overview]
Message-ID: <20091214101009.GA23742@8bytes.org> (raw)
In-Reply-To: <cover.1260662995.git.re.emese@gmail.com>
On Mon, Dec 14, 2009 at 12:59:19AM +0100, re.emese@gmail.com wrote:
> The following patch series attempts to constify several structures
> that hold function pointers. This is only the initial batch, there
> are about over 150 candidate structures, some of which can be
> constified as well, I plan to submit them in the future.
Beside the fact that you posted two patch series in one thread all your
patches lack a commit message. Please fix that.
Joerg
next prev parent reply other threads:[~2009-12-14 10:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 23:59 [PATCH 00/10] Constify struct dma_map_ops for 2.6.32-git-053fe57ac v2 re.emese
2009-12-13 23:59 ` [PATCH 01/10] " re.emese
2009-12-13 23:59 ` [PATCH 02/10] " re.emese
2009-12-13 23:59 ` [PATCH 03/10] " re.emese
2009-12-13 23:59 ` [PATCH 04/10] " re.emese
2009-12-13 23:59 ` [PATCH 05/10] " re.emese
2009-12-13 23:59 ` [PATCH 1/3] Constify struct block_device_operations " re.emese
2009-12-13 23:59 ` [PATCH 06/10] Constify struct dma_map_ops " re.emese
2009-12-13 23:59 ` [PATCH 2/3] Constify struct block_device_operations " re.emese
2009-12-13 23:59 ` [PATCH 3/3] " re.emese
2009-12-13 23:59 ` [PATCH 07/10] Constify struct dma_map_ops " re.emese
2009-12-13 23:59 ` [PATCH 08/10] " re.emese
2009-12-13 23:59 ` [PATCH 09/10] " re.emese
2009-12-13 23:59 ` [PATCH 10/10] " re.emese
2009-12-14 10:10 ` Joerg Roedel [this message]
2009-12-14 22:55 ` [PATCH 0/3] Constify struct block_device_operations " Emese Revfy
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=20091214101009.GA23742@8bytes.org \
--to=joro@8bytes.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.com \
--cc=torvalds@linux-foundation.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