mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: re.emese@gmail.com
To: linux-kernel@vger.kernel.org
Cc: Emese Revfy <re.emese@gmail.com>,
	gregkh@suse.de, torvalds@linux-foundation.org
Subject: [PATCH 2/3] Constify struct block_device_operations for 2.6.32-git-053fe57ac v2
Date: Mon, 14 Dec 2009 00:59:21 +0100	[thread overview]
Message-ID: <8b484b633f53d7b2d607d9c33f5801462e9e930c.1260662995.git.re.emese@gmail.com> (raw)
In-Reply-To: <cover.1260662995.git.re.emese@gmail.com>

From: Emese Revfy <re.emese@gmail.com>


Signed-off-by: Emese Revfy <re.emese@gmail.com>
---
 drivers/staging/dst/dcore.c             |    2 +-
 drivers/staging/hv/blkvsc_drv.c         |    2 +-
 drivers/staging/ramzswap/ramzswap_drv.c |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/dst/dcore.c b/drivers/staging/dst/dcore.c
index fd5bd0e..1be5e2c 100644
--- a/drivers/staging/dst/dcore.c
+++ b/drivers/staging/dst/dcore.c
@@ -149,7 +149,7 @@ static int dst_bdev_release(struct gendisk *disk, fmode_t mode)
 	return 0;
 }
 
-static struct block_device_operations dst_blk_ops = {
+static const struct block_device_operations dst_blk_ops = {
 	.open		= dst_bdev_open,
 	.release	= dst_bdev_release,
 	.owner		= THIS_MODULE,
diff --git a/drivers/staging/hv/blkvsc_drv.c b/drivers/staging/hv/blkvsc_drv.c
index 62b2828..0a47695 100644
--- a/drivers/staging/hv/blkvsc_drv.c
+++ b/drivers/staging/hv/blkvsc_drv.c
@@ -153,7 +153,7 @@ static int blkvsc_ringbuffer_size = BLKVSC_RING_BUFFER_SIZE;
 /* The one and only one */
 static struct blkvsc_driver_context g_blkvsc_drv;
 
-static struct block_device_operations block_ops = {
+static const struct block_device_operations block_ops = {
 	.owner = THIS_MODULE,
 	.open = blkvsc_open,
 	.release = blkvsc_release,
diff --git a/drivers/staging/ramzswap/ramzswap_drv.c b/drivers/staging/ramzswap/ramzswap_drv.c
index b839f05..c5505a9 100644
--- a/drivers/staging/ramzswap/ramzswap_drv.c
+++ b/drivers/staging/ramzswap/ramzswap_drv.c
@@ -1310,7 +1310,7 @@ out:
 	return ret;
 }
 
-static struct block_device_operations ramzswap_devops = {
+static const struct block_device_operations ramzswap_devops = {
 	.ioctl = ramzswap_ioctl,
 	.owner = THIS_MODULE,
 };
-- 
1.6.5.3


  parent reply	other threads:[~2009-12-14  0:21 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 " 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 ` re.emese [this message]
2009-12-13 23:59 ` [PATCH 06/10] Constify struct dma_map_ops " re.emese
2009-12-13 23:59 ` [PATCH 07/10] " re.emese
2009-12-13 23:59 ` [PATCH 3/3] Constify struct block_device_operations " re.emese
2009-12-13 23:59 ` [PATCH 08/10] Constify struct dma_map_ops " 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 ` [PATCH 0/3] Constify struct block_device_operations " Joerg Roedel
2009-12-14 22:55   ` 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=8b484b633f53d7b2d607d9c33f5801462e9e930c.1260662995.git.re.emese@gmail.com \
    --to=re.emese@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®