> Also that makes me wonder, if the device path is the one to the booted
> partition, wouldn't blkio point to the booted partition instead of the
> full device as well?
Yes, there are a blkio which point the same device path of the booted
partion's device path.
But our boot loader does I/O
On Tue, Feb 28, 2017 at 04:33:14PM +0100, Patrick Wildt wrote:
> On Wed, Mar 01, 2017 at 12:17:02AM +0900, YASUOKA Masahiko wrote:
> > Hi,
> >
> > On Tue, 28 Feb 2017 15:16:58 +0100
> > Patrick Wildt wrote:
> > > On Tue, Feb 28, 2017 at 10:41:21PM +0900, YASUOKA Masahiko
On Wed, Mar 01, 2017 at 12:17:02AM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> On Tue, 28 Feb 2017 15:16:58 +0100
> Patrick Wildt wrote:
> > On Tue, Feb 28, 2017 at 10:41:21PM +0900, YASUOKA Masahiko wrote:
> >> On Mon, 27 Feb 2017 11:10:31 +0100
> >> Patrick Wildt
Hi,
On Tue, 28 Feb 2017 15:16:58 +0100
Patrick Wildt wrote:
> On Tue, Feb 28, 2017 at 10:41:21PM +0900, YASUOKA Masahiko wrote:
>> On Mon, 27 Feb 2017 11:10:31 +0100
>> Patrick Wildt wrote:
>> > I'm surprised this didn't come up earlier, but I think the
On Tue, Feb 28, 2017 at 03:16:58PM +0100, Patrick Wildt wrote:
> On Tue, Feb 28, 2017 at 10:41:21PM +0900, YASUOKA Masahiko wrote:
> > Hi,
> >
> > On Mon, 27 Feb 2017 11:10:31 +0100
> > Patrick Wildt wrote:
> > > I'm surprised this didn't come up earlier, but I think the
On Tue, Feb 28, 2017 at 11:09:51PM +0900, YASUOKA Masahiko wrote:
> Let me update the diff,
>
> On Tue, 28 Feb 2017 22:41:21 +0900 (JST)
> YASUOKA Masahiko wrote:
> > On Mon, 27 Feb 2017 11:10:31 +0100
> > Patrick Wildt wrote:
> >> I'm surprised this
On Tue, Feb 28, 2017 at 10:41:21PM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> On Mon, 27 Feb 2017 11:10:31 +0100
> Patrick Wildt wrote:
> > I'm surprised this didn't come up earlier, but I think the for-loop is a
> > bit wrong. What the code is supposed to be doing is going
Let me update the diff,
On Tue, 28 Feb 2017 22:41:21 +0900 (JST)
YASUOKA Masahiko wrote:
> On Mon, 27 Feb 2017 11:10:31 +0100
> Patrick Wildt wrote:
>> I'm surprised this didn't come up earlier, but I think the for-loop is a
>> bit wrong. What the code
Hi,
On Mon, 27 Feb 2017 11:10:31 +0100
Patrick Wildt wrote:
> I'm surprised this didn't come up earlier, but I think the for-loop is a
> bit wrong. What the code is supposed to be doing is going over each
> device path node for the loaded image, which is supposed to be the
Hi,
in comparison to my usual diffs this is actually amd64 and not arm64.
I'm surprised this didn't come up earlier, but I think the for-loop is a
bit wrong. What the code is supposed to be doing is going over each
device path node for the loaded image, which is supposed to be the path
to the
10 matches
Mail list logo