From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux@armlinux.org.uk" <linux@armlinux.org.uk>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"jack@suse.cz" <jack@suse.cz>,
"zhaohongjiang@huawei.com" <zhaohongjiang@huawei.com>,
"yanaijie@huawei.com" <yanaijie@huawei.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"miaoxie@huawei.com" <miaoxie@huawei.com>
Subject: Re: [PATCH] ARM: Fix rd_size declaration
Date: Wed, 3 May 2017 19:48:44 +0000 [thread overview]
Message-ID: <1493840922.3901.33.camel@sandisk.com> (raw)
In-Reply-To: <20170503194600.16089-1-bart.vanassche@sandisk.com>
On Wed, 2017-05-03 at 12:46 -0700, Bart Van Assche wrote:
> The global variable 'rd_size' is declared as 'int' in source file
> arch/arm/kernel/atags_parse.c and as 'unsigned long' in
> drivers/block/brd.c. Fix this inconsistency. Additionally, remove
> the declarations of rd_image_start, rd_prompt and rd_doload from
> parse_tag_ramdisk() since these duplicate existing declarations
> in <linux/initrd.h>.
This is version 2 of the patch for removing the rd_size declaration.
Compared to v1, the new header file <linux/brd.h> has been dropped.
Bart.=
WARNING: multiple messages have this Message-ID (diff)
From: Bart.VanAssche@sandisk.com (Bart Van Assche)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Fix rd_size declaration
Date: Wed, 3 May 2017 19:48:44 +0000 [thread overview]
Message-ID: <1493840922.3901.33.camel@sandisk.com> (raw)
In-Reply-To: <20170503194600.16089-1-bart.vanassche@sandisk.com>
On Wed, 2017-05-03 at 12:46 -0700, Bart Van Assche wrote:
> The global variable 'rd_size' is declared as 'int' in source file
> arch/arm/kernel/atags_parse.c and as 'unsigned long' in
> drivers/block/brd.c. Fix this inconsistency. Additionally, remove
> the declarations of rd_image_start, rd_prompt and rd_doload from
> parse_tag_ramdisk() since these duplicate existing declarations
> in <linux/initrd.h>.
This is version 2 of the patch for removing the rd_size declaration.
Compared to v1, the new header file <linux/brd.h> has been dropped.
Bart.
next prev parent reply other threads:[~2017-05-03 19:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 19:46 [PATCH] ARM: Fix rd_size declaration Bart Van Assche
2017-05-03 19:46 ` Bart Van Assche
2017-05-03 19:48 ` Bart Van Assche [this message]
2017-05-03 19:48 ` Bart Van Assche
2017-06-21 20:26 ` Bart Van Assche
2017-06-21 20:26 ` Bart Van Assche
2017-06-26 9:38 ` Russell King - ARM Linux
2017-06-26 9:38 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2017-04-17 23:10 Bart Van Assche
2017-04-17 23:10 ` Bart Van Assche
2017-04-18 7:35 ` Johannes Thumshirn
2017-04-18 7:35 ` Johannes Thumshirn
2017-04-18 14:07 ` Bart Van Assche
2017-04-18 14:07 ` Bart Van Assche
2017-04-18 14:10 ` Johannes Thumshirn
2017-04-18 14:10 ` Johannes Thumshirn
2017-04-26 20:51 ` Bart Van Assche
2017-04-26 20:51 ` Bart Van Assche
2017-05-03 19:25 ` Russell King - ARM Linux
2017-05-03 19:25 ` Russell King - ARM Linux
2017-05-03 19:38 ` Bart Van Assche
2017-05-03 19:38 ` Bart Van Assche
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=1493840922.3901.33.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=miaoxie@huawei.com \
--cc=yanaijie@huawei.com \
--cc=zhaohongjiang@huawei.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.