Commit d2e8071bed0be ("tpm: make all 'class' structures const")
unfortunately had a typo for the name on tpmrm.
Fixes: d2e8071bed0b ("tpm: make all 'class' structures const")
Signed-off-by: Justin M. Forbes
---
drivers/char/tpm/tpm-chip.c | 2 +-
1
Commit d2e8071bed0be ("tpm: make all 'class' structures const")
unfortunately had a typo for the name on tpmrm.
Fixes: d2e8071bed0b ("tpm: make all 'class' structures const")
Signed-off-by: Justin M. Forbes
---
drivers/char/tpm/tpm-chip.c | 2 +-
1
The top level tools/Makefile includes kvm_stat as a target in help, but
the actual target is missing.
Signed-off-by: Justin M. Forbes
---
tools/Makefile | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/Makefile b/tools/Makefile
index 00caacd..c8a90d0 100644
--- a
> drivers/block/loop.c | 30 ++
> drivers/block/loop.h | 1 +
> 2 files changed, 15 insertions(+), 16 deletions(-)
>
>
> Thanks,
> Ming Lei
>
Tested with Fedora 22 ISOs, these still solve the problem for us.
Tested-by: Justin M. For
On Sun, 2015-04-26 at 23:27 +0800, Ming Lei wrote:
> Hi Justin,
>
> On Fri, 24 Apr 2015 16:46:02 -0500
> "Justin M. Forbes" wrote:
>
> > On Fri, 2015-04-24 at 10:59 +0800, Ming Lei wrote:
> > > Hi Justin,
> > >
> > > Thanks for t
On Fri, 2015-04-24 at 10:59 +0800, Ming Lei wrote:
> Hi Justin,
>
> Thanks for the report.
>
> On Thu, 23 Apr 2015 16:04:10 -0500
> "Justin M. Forbes" wrote:
>
> > The block-mq conversion for loop in 4.0 kernels is showing us an
> > interesting scal
The block-mq conversion for loop in 4.0 kernels is showing us an
interesting scalability problem with live CDs (ro, squashfs). It was
noticed when testing the Fedora beta that the more CPUs a liveCD image
was given, the slower it would boot. A 4 core qemu instance or bare
metal instance took more
On Fri, Jul 12, 2013 at 04:28:20PM -0400, Steven Rostedt wrote:
>
> I would suspect that machines that allow unprivileged users would be
> running distro kernels, and not the latest release from Linus, and thus
> even a bug that "can allow an unprivileged user to crash the kernel" may
> still be a
On Fri, 2012-09-07 at 16:44 +0100, Jan Beulich wrote:
> >>> On 07.09.12 at 16:22, "Justin M. Forbes" wrote:
> > On Fri, Sep 07, 2012 at 03:02:29PM +0100, Jan Beulich wrote:
> >> >>> On 07.09.12 at 15:21, Stefan Bader wrote:
> >> > On 07.0
On Fri, Sep 07, 2012 at 03:02:29PM +0100, Jan Beulich wrote:
> >>> On 07.09.12 at 15:21, Stefan Bader wrote:
> > On 07.09.2012 14:33, Jan Beulich wrote:
> > On 07.09.12 at 13:40, Stefan Bader wrote:
> >>> When writing unsupported flags into CR4 (for some time the
> >>> xen_write_cr4 function
for , we have verified cases on inteldrmfb, radeondrmfb, and
cirrusdrmfb.
This is the last message displayed before the system hangs. This seems
to be hitting a large number of users in Fedora, though certainly not
everyone. This started happening with the 3.5 updates, and is still an
issue. It
On Fri, 2008-02-01 at 17:30 -0800, Christoph Lameter wrote:
> On Fri, 1 Feb 2008, Justin M. Forbes wrote:
>
> >
> > On Fri, 2008-02-01 at 16:39 -0800, Christoph Lameter wrote:
> > > NO! Wrong fix. Was dropped from mainline.
> >
> > What is the right fix
On Fri, 2008-02-01 at 16:39 -0800, Christoph Lameter wrote:
> NO! Wrong fix. Was dropped from mainline.
What is the right fix for the OOM issues with 2.6.22? Perhaps
http://marc.info/?l=linux-mm&m=119973653803451&w=2 should be added to
the queue in its place? The OOM issue in 2.6.22 is real, and
On Mon, Aug 20, 2007 at 11:52:10PM -0700, Greg KH wrote:
> This is the start of the stable review cycle for the 2.6.22.5 release.
No roll up patch for this one?
Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
his stable series, we should indeed
leave it out. That said, I will be testing this patch a bit further
myself, and because it does address a real memory leak issue, we should
consider it or another fix for stable 2.6.12.4.
Justin M. Forbes
-
To unsubscribe from this list: send the line "unsubsc
.
I would propose that the new stable series kernels move the .x version
information somewhere more official. I certainly do not mind throwing
together a patch to support DOTVERSION or what ever people want to call it.
Is anyone opposed to such a change?
Thanks,
Justin M. Forbes
-
To unsubscribe
16 matches
Mail list logo