From: Daniel Vetter <daniel@ffwll.ch>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: David Airlie <airlied@linux.ie>,
arcml <linux-snps-arc@lists.infradead.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [GIT PULL] drm/arc: Yet another set of minor fixes
Date: Mon, 16 Dec 2019 11:28:58 +0100 [thread overview]
Message-ID: <20191216102858.GR624164@phenom.ffwll.local> (raw)
In-Reply-To: <CY4PR1201MB01206B89011211BB25EF82ADA1540@CY4PR1201MB0120.namprd12.prod.outlook.com>
On Fri, Dec 13, 2019 at 10:24:42AM +0000, Alexey Brodkin wrote:
> Hi Daniel,
>
> > -----Original Message-----
> > From: Daniel Vetter <daniel@ffwll.ch>
> > Sent: Friday, December 13, 2019 1:22 PM
> > To: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Daniel Vetter <daniel@ffwll.ch>; David Airlie <airlied@linux.ie>; arcml <linux-snps-
> > arc@lists.infradead.org>; Eugeniy Paltsev <paltsev@synopsys.com>; dri-devel@lists.freedesktop.org
> > Subject: Re: [GIT PULL] drm/arc: Yet another set of minor fixes
> >
>
> [snip]
>
> > > Not sure if you noticed re-spin of my pull-request in the previous message.
> > > Do you want me to send it in a separate email?
> >
> > Yeah I guess this got lost again.
>
> So should I re-send it in another email or you will pick it up
> from existing thread?
>
> If I'm going to re-send it do I need to re-base it on today's drm/drm-next?
I just tried to vacuum it in, but it chokes the scripts since it's
multiple pull requests in one mail with quotes. So please redo in a clean
mail.
Wrt baseline, here's the recommendation in order of my preference:
- Just stuff it into drm-misc-next
- Base your tree on a tag from Linux
- If you need a specific depedency, base your tree on drm-next with that
patch included.
- If it's even more complicated, do a multi-way topic branch with lots of
coordination.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2019-12-16 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 7:48 [GIT PULL] drm/arc: Yet another set of minor fixes Alexey Brodkin
2019-11-27 10:06 ` Daniel Vetter
2019-11-27 13:49 ` Alexey Brodkin
2019-11-27 14:06 ` Daniel Vetter
2019-12-13 10:20 ` Alexey Brodkin
2019-12-13 10:22 ` Daniel Vetter
2019-12-13 10:24 ` Alexey Brodkin
2019-12-16 10:28 ` Daniel Vetter [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=20191216102858.GR624164@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-snps-arc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).