lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440809101101ld5a98d0yfd9089b6ab8eac1c@mail.gmail.com>
Date:	Wed, 10 Sep 2008 11:01:26 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Jesse Barnes" <jbarnes@...tuousgeek.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [PATCH] pci: fix merging left out for BAR print out v2

On Wed, Sep 10, 2008 at 10:48 AM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> On Wednesday, September 10, 2008 1:44 am Ingo Molnar wrote:
>> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
>> > print out for Device BAR address before kernel try to update them.
>> >
>> > also change it to KERN_DEBUG instead...
>> >
>> > v2: update to linux-pci next
>> >    also add (unsigned long long) cast
>> >
>> > Signed-off-by: Yinghai Lu <yhlu.kernel@...il.com>
>>
>> Jesse, if you want to pick it up, could we please do this via git
>> methods (git-pull and stuff)? The commit below is the one in -tip -
>> should i separate it out?
>
> Sure, though I'm not sure why I shouldn't just be applying this stuff to my
> tree first... Seems weird to pull from you only to then ask Linus to pull.

there is another patch applied to linux-pci next for cast some
resource_t to unsigned-long-long...

anyway, v2 could be applied to linux-pci cleanly.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ