From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] block: pass block dev not num to read/write/erase()
Date: Wed, 13 Jan 2016 11:29:59 -0700 [thread overview]
Message-ID: <569697A7.1050305@wwwdotorg.org> (raw)
In-Reply-To: <20151218002741.GA11783@bill-the-cat>
On 12/17/2015 05:27 PM, Tom Rini wrote:
> On Mon, Dec 07, 2015 at 11:38:48AM -0700, Stephen Warren wrote:
>
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This will allow the implementation to make use of data in the block_dev
>> structure beyond the base device number. This will be useful so that eMMC
>> block devices can encompass the HW partition ID rather than treating this
>> out-of-band. Equally, the existence of the priv field is crying out for
>> this patch to exist.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Tom,
I assume you were just waiting for the merge window to open before
applying this?
next prev parent reply other threads:[~2016-01-13 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 18:38 [U-Boot] [PATCH 1/3] block: pass block dev not num to read/write/erase() Stephen Warren
2015-12-07 18:38 ` [U-Boot] [PATCH 2/3] mmc: store hwpart in the block device Stephen Warren
2015-12-18 0:27 ` Tom Rini
2016-01-14 13:21 ` [U-Boot] [U-Boot,2/3] " Tom Rini
2015-12-07 18:38 ` [U-Boot] [PATCH 3/3] ums: support multiple LUNs at once Stephen Warren
2015-12-18 0:27 ` Tom Rini
2016-01-14 13:21 ` [U-Boot] [U-Boot,3/3] " Tom Rini
2015-12-18 0:27 ` [U-Boot] [PATCH 1/3] block: pass block dev not num to read/write/erase() Tom Rini
2016-01-13 18:29 ` Stephen Warren [this message]
2016-01-13 19:43 ` Tom Rini
2016-01-14 13:20 ` [U-Boot] [U-Boot, " Tom Rini
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=569697A7.1050305@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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.