From: "Bjørn Mork" <bjorn@mork.no>
To: Greg KH <greg@kroah.com>
Cc: linux-media@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH v2] V4L/DVB: budget: Oops: "BUG: unable to handle kernel NULL pointer dereference"
Date: Thu, 22 Apr 2010 10:53:44 +0200 [thread overview]
Message-ID: <874oj350mf.fsf@nemi.mork.no> (raw)
In-Reply-To: <20100419182140.GE32347@kroah.com> (Greg KH's message of "Mon, 19 Apr 2010 11:21:40 -0700")
Greg KH <greg@kroah.com> writes:
> Any reason why this patch isn't in Linus's tree yet?
Not to my knowledge. Anyone?
I must admit that I do not entirely understand the flow of bugfix
patches for V4L/DVB. There doesn't seem to be any collection point for
those, only a git tree for development and a mercurial tree for a
backported version of the development tree. Is that correct, or is the
reason this patch isn't merged that I missed something here?
I do note that MAINTAINERS point to
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git but
this tree doesn't seem to be actually used? No bugfixes for any part of
the subsystem in 2.5 months seems unlikely...
Sorry if I've missed this in any of the V4L development docs. I'd
really appreciate it if anyone pointed me in the right direction.
Bjørn
prev parent reply other threads:[~2010-04-22 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 10:57 [PATCH] V4L/DVB: budget: Oops: "BUG: unable to handle kernel NULL pointer dereference" Bjørn Mork
2010-03-24 12:25 ` Oliver Endriss
2010-03-24 12:30 ` Bug#575207: Info received ([PATCH] V4L/DVB: budget: Oops: "BUG: unable to handle kernel NULL pointer dereference") Debian Bug Tracking System
2010-03-24 13:17 ` [PATCH v2] V4L/DVB: budget: Oops: "BUG: unable to handle kernel NULL pointer dereference" Bjørn Mork
2010-03-24 13:30 ` [PATCH v2 for v4l-dvb master] " Bjørn Mork
2010-03-25 12:38 ` Oliver Endriss
2010-04-19 18:21 ` [stable] [PATCH v2] " Greg KH
2010-04-22 8:53 ` Bjørn Mork [this message]
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=874oj350mf.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=greg@kroah.com \
--cc=linux-media@vger.kernel.org \
--cc=stable@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox