lude the fix
if CONFIG_MGEODEGX1 or CONFIG_X86_GENERIC are set, thus fixing the
problem.
Signed-off-by: David Woodhouse
Cc: stable@vger.kernel.org
---
I'm slightly concerned about bypassing verification though, when the
reason I *noticed* this issue is because the verification *failed*:
[8.893
On Tue, 2015-02-10 at 12:49 -0800, a...@linux-foundation.org wrote:
> From: Chen Jie
> Subject: jffs2: fix handling of corrupted summary length
>
> sm->offset maybe wrong but magic maybe right, the offset do not have
> CRC.
Applied; thanks.
--
David Woodhouse
ing the missing flush.
Signed-off-by: David Woodhouse
---
For 3.14 and earlier. As noted, this fix is in 3.15 already.
drivers/iommu/intel-iommu.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.
On Fri, 2013-10-25 at 21:41 -0400, Huang Shijie wrote:
> On Fri, Oct 25, 2013 at 02:29:42PM +0100, David Woodhouse wrote:
> > On Fri, 2013-10-25 at 21:33 -0400, Huang Shijie wrote:
> > >
> > > I am ok with your patch. but we will meet a compiler
On Thu, 2013-10-24 at 15:19 -0700, Brian Norris wrote:
> I fixed up the language a little, dropped the 'stable', and pushed to
> linux-mtd.git (in hopes of sending another pull request for 3.12). I'll
> see if David wants to weigh in first.
You're fine. Go ahead and send the request if you're happ
On Fri, 2013-10-25 at 21:33 -0400, Huang Shijie wrote:
>
> I am ok with your patch. but we will meet a compiler warning, since
> the set_geometry_by_ecc_info() is not referenced.
Yeah, I predicted that but at this stage with *hours* to catch Linux and
get it into 3.12, I think that's the bett
On Fri, 2013-10-25 at 13:03 +0100, David Woodhouse wrote:
>
> So... what if someone has already shipped the new chips that require
> stronger ECC, without realising that legacy_set_geometry() is
> insufficient? (And is legacy_set_geometry *actually* doing precisely the
> sa
roperty exists in the device tree.
--
David WoodhouseOpen Source Technology Centre
david.woodho...@intel.com Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
On Wed, 2013-07-17 at 11:51 -0700, Sarah Sharp wrote:
> No, it's actually some of the comments I've received that bother me.
> For example, I would never want to deal with the misogynist troll,
> Lubin, EVER again.
It surprises me to see you calling someone names like that, Sarah. It
seems to be c
On Mon, 2013-07-15 at 13:19 -0700, Guenter Roeck wrote:
> That seems to be a bit drastic. It is quite useful to have the tag,
> but maybe it should only be added by the maintainer and not in the initial
> patch submission. This would ensure that the maintainer(s) made the decision.
> If the origina
On Mon, 2013-04-15 at 15:35 -0700, Greg Kroah-Hartman wrote:
> On Mon, Apr 15, 2013 at 09:55:20PM +0100, David Woodhouse wrote:
> > On Sun, 2013-04-14 at 19:17 -0700, Greg Kroah-Hartman wrote:
> > > 3.0-stable review patch. If anyone has any objections, please let
> me know
On Sun, 2013-04-14 at 19:17 -0700, Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
Please use f5cf8f07423b2677cebebcebc863af77223a4972 instead (for 3.4
too).
--
dwmw2
smime.p7s
Description: S/MIME cryptographic signature
On Thu, 2013-03-14 at 17:22 +0100, Alexander Holler wrote:
>
> Agreed (thats what my patch did).
>
> I've introduced a new config option because I don't know if something (a
> use case I don't know) relies on the validity check of the dates in the
> parser. If there currently isn't such a user,
support entirely.
Some use cases *might* want to check the dates, and should be permitted
to do so. Just don't refuse to even *parse* the key outside its valid
date range... :)
--
David WoodhouseOpen Source Technology Centre
david.woodho...@intel.com
msg33138.html
> Cc: stable@vger.kernel.org
> Cc: David Woodhouse
> Reported-and-tested-by: Mihai Moldovan
> Signed-off-by: Daniel Vetter
> ---
> drivers/iommu/intel-iommu.c |8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iomm
On Sun, 2013-01-20 at 23:50 +0100, Daniel Vetter wrote:
> DMAR support on g4x/gm45 integrated gpus seems to be totally busted.
> So don't bother, but instead disable it by default to allow distros to
> unconditionally enable DMAR support.
Acked-By: David Woodhouse
It *really* wi
16 matches
Mail list logo
