From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Wed, 19 Sep 2012 11:18:51 -0600 Subject: [U-Boot] [PATCH V3 3/8] disk: introduce get_device() In-Reply-To: <50591F0B.7060504@gmail.com> References: <1348007874-20466-1-git-send-email-swarren@wwwdotorg.org> <1348007874-20466-4-git-send-email-swarren@wwwdotorg.org> <50591E2E.3070208@gmail.com> <50591F0B.7060504@gmail.com> Message-ID: <5059FE7B.4050403@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 09/18/2012 07:25 PM, Rob Herring wrote: > On 09/18/2012 08:21 PM, Rob Herring wrote: >> On 09/18/2012 05:37 PM, Stephen Warren wrote: >>> From: Stephen Warren >>> >>> This patch introduces function get_device(). This looks up a >>> block_dev_desc_t from an interface name (e.g. mmc) and device number >>> (e.g. 0). This function is essentially the non-partition-specific >>> prefix of get_device_and_partition(). >> >> Then shouldn't get_device_and_partition just call get_device. Perhaps >> create get_partition() and then get_device_and_partition is just a wrapper. >> > > I should read all the way through the series before replying... > > Anyway, I would squash it all unless you want to have restructuring with > current functionality and then enhancements. OK, I'm happy to squash everything together, and repost a series with both your and my patches; I separated it out to hopefully make working out what changes I made a little easier. I did wonder about creating separate get_device, get_partition, and get_device_or_partition functions, the latter probably using a common implementation. I guess if I squash my changes into your original patches, then creating those 3 separate functions would end up being less churn. So, unless there are objections, I'll do that.