> On Mar 14, 2018, at 2:08 AM, Jani Nikula wrote:
>
> In qf line 411:
> git reset --hard $(git rev-parse --abbrev-ref @{u})
> ^-- SC1083: This { is literal. Check expression (missing ;/\n?) or quote it.
> ^-- SC1083: This } is literal. Check expression (missing ;/\n?) or quote it.
>
Sorry :(
> On Aug 27, 2018, at 1:34 AM, Nikula, Jani wrote:
>
>> On Mon, 27 Aug 2018, Daniel Vetter wrote:
>>> On Fri, Aug 24, 2018 at 02:43:35PM -0700, Rodrigo Vivi wrote:
>>> Besides drm-intel-next, sometimes it is used to re-use an
>>> already existent tag that you just created outside
>>> or in cas
> On Aug 27, 2018, at 1:39 AM, Nikula, Jani wrote:
>
>> On Mon, 27 Aug 2018, Daniel Vetter wrote:
>>> On Fri, Aug 24, 2018 at 02:43:34PM -0700, Rodrigo Vivi wrote:
>>> I don't understand exactly why we need this special handling only
>>> for drm-intel-next. But let's at least consolidate this
Much better indeed.
Reviewed-by: Rodrigo Vivi
> On Nov 13, 2019, at 9:48 AM, Daniel Vetter wrote:
>
> On Thu, Sep 19, 2019 at 9:35 PM Daniel Vetter wrote:
>>
>> Dave asked me how to fix a screwed-up rerere, and I noticed that the
>> wording/spelling is a bit sub-par.
>>
>> Signed-off-by: Da
On Nov 18, 2019, at 12:14 PM, Lucas De Marchi
mailto:lucas.demar...@intel.com>> wrote:
On Mon, Nov 18, 2019 at 04:57:34PM +0200, Jani Nikula wrote:
On Fri, 15 Nov 2019, Lucas De Marchi
mailto:lucas.demar...@intel.com>> wrote:
Add method add-link-head that applies the link to head without any
a
> On Sep 16, 2020, at 7:00 AM, Jani Nikula wrote:
>
> On Wed, 16 Sep 2020, Rodrigo Vivi wrote:
>> On Wed, Sep 16, 2020 at 12:57:43PM +0300, Jani Nikula wrote:
>>> Email messages need two levels of decoding: First, content transfer
>>> encoding, such as base64 or quoted-printable. Second, char
Apparently #x86-32 as comment is breaking dim on the fixes flow.
$ tdim push drm-intel-next-fixes
dim: d6ec212e4a0d ("drm/i915/gem: Avoid implicit vmap for highmem on x86-32"):
Subject in fixes line doesn't match referenced commit:
dim: fb8621d3bee8 ("drm/i915: Avoid allocating a vmap arena
On Oct 28, 2020, at 12:46 AM, Jani Nikula
mailto:jani.nik...@intel.com>> wrote:
On Tue, 27 Oct 2020, Rodrigo Vivi
mailto:rodrigo.v...@intel.com>> wrote:
On Mon, Oct 26, 2020 at 12:21:24PM +0200, Jani Nikula wrote:
On Wed, 16 Sep 2020, Rodrigo Vivi
mailto:rodrigo.v...@intel.com>> wrote:
On Wed
> On Nov 12, 2020, at 4:32 PM, Dave Airlie wrote:
>
> On Fri, 13 Nov 2020 at 09:08, Rodrigo Vivi wrote:
>>
>> Hi Dave and Daniel,
>>
>> This is the same set as last week + couple new fixes targeting stable.
>>
>
> But I merged last weeks set and it's in rc3, maybe you can generate
> the p
On Wed, 2020-12-09 at 14:11 +0200, Ville Syrjälä wrote:
> On Thu, Dec 03, 2020 at 05:47:05AM -0800, Rodrigo Vivi wrote:
> > Hi Dave and Daniel,
> >
> > Please ignore the pull request I had sent yesterday and use only
> > this one.
> >
> > I had missed one patch: 14d1eaf08845 ("drm/i915/gt: Protec
On Wed, 2021-08-11 at 13:58 +0300, Jani Nikula wrote:
> It's not exactly trivial to add the smarts to properly check for
> pushing
> backmerges, rebases, topic branches and subtree branches (such as
> gvt). For a start, prompt the user with hints about what's going on.
>
> Cc: Daniel Vetter
> Sig
On Tue, 2022-02-22 at 11:44 -0800, Lucas De Marchi wrote:
> On Mon, Feb 21, 2022 at 11:21:35AM +0200, Jani Nikula wrote:
> > On Mon, 21 Feb 2022, Dave Airlie wrote:
> > > On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen
> > > wrote:
> > > >
> > > > Hi Dave & Daniel,
> > > >
> > > > Here is the fir
Hi Anusha,
first of all, I'm afraid that dim-tools is not the best place
for this kind of queries. Probably something like #freedesktop
channel at oftc.irc would be better. but more below
On Tue, 2022-03-01 at 00:06 +, Srivatsa, Anusha wrote:
> I see the error: anush...@git.freedesktop.or
On Wed, 2022-07-13 at 17:31 -0400, Rodrigo Vivi wrote:
> Hi Dave and Daniel,
>
> On behalf of Tvrtko, who is recovering from Covid,
> here goes the latest drm-intel-gt-next pull request
> targeting 5.20.
Hi Folks,
any particular issue with this pull request?
We just realized it is not yet part
On Sun, 2022-09-11 at 19:22 +0200, Jason A. Donenfeld wrote:
> Hi Rodrigo,
>
> On Thu, Sep 08, 2022 at 09:59:54AM -0400, Rodrigo Vivi wrote:
> > Hi Dave and Daniel,
> >
> > A few fixes, but most targeting stable.
> >
> > [...]
> >
> > Ville Syrjälä (2):
> > drm/i915: Implement WaEdpLinkRa
On Tue, 2022-10-04 at 11:01 -0700, Ceraolo Spurio, Daniele wrote:
>
>
> On 10/4/2022 10:48 AM, Rodrigo Vivi wrote:
> > On Mon, Oct 03, 2022 at 11:50:19AM -0700, Daniele Ceraolo Spurio
> > wrote:
> > > The check_maintainer warns the user if any of the patches being
> > > applied
> > > touches file
On Wed, 2022-10-05 at 14:12 +0200, Daniel Vetter wrote:
> On Mon, Aug 08, 2022 at 03:00:02PM -0400, Rodrigo Vivi wrote:
> > In case a fix was not propagated yet to upstream, the
> > original commit sha won't be found hence the fix of this
> > fix will be missed during the cherry-pick.
> >
> > Sinc
On Sat, 2022-10-29 at 02:41 +0300, Ville Syrjälä wrote:
> On Fri, Oct 28, 2022 at 02:22:33PM -0400, Rodrigo Vivi wrote:
> > Hi Dave and Daniel,
> >
> > Here goes the first chunk of drm-intel-next targeting 6.2
> >
> > The highlight goes to Ville with many display related clean-up
> > and improvem
On Fri, 2022-12-30 at 06:55 -0500, Rodrigo Vivi wrote:
> In case a fix was not propagated yet to upstream, the
> original commit sha won't be found hence the fix of this
> fix will be missed during the cherry-pick.
>
> Since dim cherry-picks reliably adds the -x "(cherry picked
> from" message, le
19 matches
Mail list logo
