From: jani.nikula@linux.intel.com (Jani Nikula)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/bridge: dw-hdmi: fix EDID parsing
Date: Fri, 10 Nov 2017 11:45:27 +0200 [thread overview]
Message-ID: <87zi7u8o20.fsf@intel.com> (raw)
In-Reply-To: <20171109162634.GC12318@n2100.armlinux.org.uk>
On Thu, 09 Nov 2017, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> On Thu, Nov 09, 2017 at 02:12:45PM +0200, Jani Nikula wrote:
>> And as I said elsewhere in the thread, Russell's patch may be relevant
>> for current Linus' master and stable. We just need to reconciliate how
>> the two things should work together in drm-next and v4.15 and on.
>
> Exactly, the patch is intended for current kernels. The hint is that
> (a) it's a bug fix, (b) it says "fix" in the title, and (c) it has the
> stable attributation which says "apply me to previous kernels".
>
> Daniel's response effectively says "no, we're not going to accept the
> patch, work on a fix with some development code."
Please don't turn a technical discussion into an unnecessary
altercation. Focusing on finding the best solution instead would be much
appreciated.
> So, unless someone wants to tell me that it's acceptable to develop bug
> fixes against Linus' tree _for_ Linus' tree and accept this patch, or
> show some other solution that can be applied to Linus' current tree and
> backported to stable trees, I'm just not going to bother in future -
> someone else can end up doing the work.
I also don't want non-regression fixes merged to Linus' tree if they're
known to regress much wider impact work queued to Linus' tree for the
next merge window. And it's not just some development code, it's been in
drm-next and linux-next for more than 1? months now. So I want to figure
this out first.
Lu?s, can you try try drm-next *with* Russell's patch, please?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: "David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Luís Mendes" <luis.p.mendes@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/bridge: dw-hdmi: fix EDID parsing
Date: Fri, 10 Nov 2017 11:45:27 +0200 [thread overview]
Message-ID: <87zi7u8o20.fsf@intel.com> (raw)
In-Reply-To: <20171109162634.GC12318@n2100.armlinux.org.uk>
On Thu, 09 Nov 2017, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> On Thu, Nov 09, 2017 at 02:12:45PM +0200, Jani Nikula wrote:
>> And as I said elsewhere in the thread, Russell's patch may be relevant
>> for current Linus' master and stable. We just need to reconciliate how
>> the two things should work together in drm-next and v4.15 and on.
>
> Exactly, the patch is intended for current kernels. The hint is that
> (a) it's a bug fix, (b) it says "fix" in the title, and (c) it has the
> stable attributation which says "apply me to previous kernels".
>
> Daniel's response effectively says "no, we're not going to accept the
> patch, work on a fix with some development code."
Please don't turn a technical discussion into an unnecessary
altercation. Focusing on finding the best solution instead would be much
appreciated.
> So, unless someone wants to tell me that it's acceptable to develop bug
> fixes against Linus' tree _for_ Linus' tree and accept this patch, or
> show some other solution that can be applied to Linus' current tree and
> backported to stable trees, I'm just not going to bother in future -
> someone else can end up doing the work.
I also don't want non-regression fixes merged to Linus' tree if they're
known to regress much wider impact work queued to Linus' tree for the
next merge window. And it's not just some development code, it's been in
drm-next and linux-next for more than 1½ months now. So I want to figure
this out first.
Luís, can you try try drm-next *with* Russell's patch, please?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-10 9:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:27 [PATCH] drm/bridge: dw-hdmi: fix EDID parsing Russell King
2017-11-07 11:27 ` Russell King
2017-11-09 6:49 ` Archit Taneja
2017-11-09 6:49 ` Archit Taneja
2017-11-09 8:23 ` Daniel Vetter
2017-11-09 8:23 ` Daniel Vetter
2017-11-09 9:31 ` Russell King - ARM Linux
2017-11-09 9:31 ` Russell King - ARM Linux
2017-11-09 9:49 ` Jani Nikula
2017-11-09 9:49 ` Jani Nikula
2017-11-09 9:51 ` Luís Mendes
2017-11-09 10:52 ` Luís Mendes
2017-11-09 10:52 ` Luís Mendes
2017-11-09 11:07 ` Luís Mendes
2017-11-09 11:07 ` Luís Mendes
2017-11-09 12:12 ` Jani Nikula
2017-11-09 12:12 ` Jani Nikula
2017-11-09 14:34 ` Luís Mendes
2017-11-09 14:34 ` Luís Mendes
2017-11-09 15:01 ` Jani Nikula
2017-11-09 15:01 ` Jani Nikula
2017-11-09 15:08 ` Luís Mendes
2017-11-09 15:22 ` Jani Nikula
2017-11-09 16:17 ` Daniel Vetter
2017-11-09 22:44 ` Luís Mendes
2017-11-10 9:37 ` Daniel Vetter
2017-11-09 16:28 ` Russell King - ARM Linux
2017-11-09 16:28 ` Russell King - ARM Linux
2017-11-09 18:45 ` Luís Mendes
2017-11-09 18:45 ` Luís Mendes
2017-11-09 16:26 ` Russell King - ARM Linux
2017-11-09 16:26 ` Russell King - ARM Linux
2017-11-10 9:45 ` Jani Nikula [this message]
2017-11-10 9:45 ` Jani Nikula
2017-11-09 8:27 ` Jani Nikula
2017-11-09 8:27 ` Jani Nikula
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=87zi7u8o20.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.