Gerd Hoffmann writes:
> On Fr, 2017-01-27 at 14:53 +0100, Daniel Vetter wrote:
>> On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
>> > On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
>> > > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
>>
Hi,
> > Does dim detect that a Link: tag is already present and doesn't add
> > another one then?
>
> Nope. Patches welcome. ;)
For now I've settled to applying patches with the patches tool, a little
shell script to rewrite "Message-id:" lines into patchwork links, and
using dim to push updat
On Fr, 2017-01-27 at 14:53 +0100, Daniel Vetter wrote:
> On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
> > On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
> > > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> > > output"). qxl_num_crtc de
On Tue, 31 Jan 2017, Gerd Hoffmann wrote:
> Hi,
>
>> declare -n introduced in bash 4.3 is needed for alias
>> support. Workaround at [1].
>>
>> [1] https://lists.freedesktop.org/archives/intel-gfx/2017-January/118474.html
>
> Works for me. Thanks.
Thanks, pushed.
>> N.b. dim currently doesn'
Hi,
> declare -n introduced in bash 4.3 is needed for alias
> support. Workaround at [1].
>
> [1] https://lists.freedesktop.org/archives/intel-gfx/2017-January/118474.html
Works for me. Thanks.
> N.b. dim currently doesn't do all its magic, such as adding Link: tag,
> if you apply more than
On Tue, 31 Jan 2017, Gerd Hoffmann wrote:
> Hi,
>
>> branches. One part that imo really should stick around is the drm-tip
>> integration tree rebuilding. That allows us to distribute conflict
>> handling (e.g. between drm-misc-fixes and drm-misc-next), and with more
>> people and more drivers i
On Tue, Jan 31, 2017 at 09:55:46AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > branches. One part that imo really should stick around is the drm-tip
> > integration tree rebuilding. That allows us to distribute conflict
> > handling (e.g. between drm-misc-fixes and drm-misc-next), and with more
> >
Hi,
> branches. One part that imo really should stick around is the drm-tip
> integration tree rebuilding. That allows us to distribute conflict
> handling (e.g. between drm-misc-fixes and drm-misc-next), and with more
> people and more drivers in drm-misc I expect more conflicts.
Ok, good poin
On Mon, Jan 30, 2017 at 06:14:49PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > drm-misc runs with the committer model, i.e. a few maintainers to do pull
> > requests and backmerges, a big pile of people directly pushing patches.
>
> [ looked at docs too meanwhile ]
>
> Sounds good. I guess switch
Hi,
> drm-misc runs with the committer model, i.e. a few maintainers to do pull
> requests and backmerges, a big pile of people directly pushing patches.
[ looked at docs too meanwhile ]
Sounds good. I guess switching over simplifies things for all of us.
We'll avoid issues like the one at ha
On Mon, Jan 30, 2017 at 10:41:18AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > I guess I could ask Gerd whether we wants to be part of the experiment to
> > maintain small drivers in drm-misc, to avoid these kinds of coordination
> > issues?
>
> Sounds reasonable. There isn't much activity, that's
Hi,
> I guess I could ask Gerd whether we wants to be part of the experiment to
> maintain small drivers in drm-misc, to avoid these kinds of coordination
> issues?
Sounds reasonable. There isn't much activity, that's why I've grouped
all four qemu drivers into a single branch already.
The do
On Fri, Jan 27, 2017 at 02:41:29PM -0200, Gabriel Krisman Bertazi wrote:
> Daniel Vetter writes:
> > On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
> >> On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
> >> > No longer true since commit 07f8d9bdb235 ("drm/qxl: add s
Hi,
> Do you want to merge from drm-misc or should we push this one
> directly via drm-misc?
Merging through drm-misc is fine with me.
cheers,
Gerd
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/li
Daniel Vetter writes:
> On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
>> On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
>> > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
>> > output"). qxl_num_crtc defaults to 4 and is configurable as
On Fri, Jan 27, 2017 at 09:20:42AM +0100, Gerd Hoffmann wrote:
> On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
> > No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> > output"). qxl_num_crtc defaults to 4 and is configurable as a module
> > parameter.
>
>
On Do, 2017-01-26 at 23:05 -0200, Gabriel Krisman Bertazi wrote:
> No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> output"). qxl_num_crtc defaults to 4 and is configurable as a module
> parameter.
Picked up patches 1-3 for drm-qemu branch.
Patch 4 doesn't apply and seem
On Thu, Jan 26, 2017 at 11:05:45PM -0200, Gabriel Krisman Bertazi wrote:
> No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> output"). qxl_num_crtc defaults to 4 and is configurable as a module
> parameter.
>
> Signed-off-by: Gabriel Krisman Bertazi
Since I ended up read
On Thu, Jan 26, 2017 at 11:05:45PM -0200, Gabriel Krisman Bertazi wrote:
> No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
> output"). qxl_num_crtc defaults to 4 and is configurable as a module
> parameter.
>
> Signed-off-by: Gabriel Krisman Bertazi
> ---
> drivers/gpu/d
No longer true since commit 07f8d9bdb235 ("drm/qxl: add support for > 1
output"). qxl_num_crtc defaults to 4 and is configurable as a module
parameter.
Signed-off-by: Gabriel Krisman Bertazi
---
drivers/gpu/drm/qxl/qxl_fb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dri
20 matches
Mail list logo
