From: Andrew Morton <akpm@linux-foundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: daniel.lezcano@linaro.org, narmstrong@baylibre.com,
airlied@linux.ie, catalin.marinas@arm.com,
Alexey.Brodkin@synopsys.com, will.deacon@arm.com,
fbarrat@linux.vnet.ibm.com, oleg@redhat.com, paulus@ozlabs.org,
yamada.masahiro@socionext.com, mhocko@suse.com,
viresh.kumar@linaro.org, Pavel Machek <pavel@ucw.cz>,
hpa@zytor.com, JinHuiEric.Huang@amd.com, Rex.Zhu@amd.com,
elfring@users.sourceforge.net, scott.bauer@intel.com,
linux-arm-kernel@lists.infradead.org, mpe@ellerman.id.au,
x86@kernel.org, Wenjing.Liu@amd.com, linux@armlinux.org.uk,
amd-gfx@lists.freedesktop.org, Ding.Wang@amd.com, aik@ozlabs.ru,
wens@csie.org, mingo@redhat.com, vbabka@suse.cz,
airlied@redhat.com, ruscur@russell.cc, shli@kernel.org,
dan.carpenter@oracle.com, andresx7@gmail.com,
linux-arm-msm@vger.kernel.org, axboe@kernel.dk,
linux-efi@vger.kernel.org, alistair@popple.id.au,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] fix double ;;s in code
Date: Tue, 20 Feb 2018 15:47:15 -0800 [thread overview]
Message-ID: <20180220154715.2a8ecd75a1c2cc698baefd26@linux-foundation.org> (raw)
In-Reply-To: <87o9kkcck3.fsf@intel.com>
On Tue, 20 Feb 2018 10:03:56 +0200 Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 19 Feb 2018, Pavel Machek <pavel@ucw.cz> wrote:
> > On Mon 2018-02-19 16:41:35, Daniel Vetter wrote:
> >> Yeah, pls split this into one patch per area, with a suitable patch
> >> subject prefix. Look at git log of each file to get a feeling for what's
> >> the standard in each area.
> >
> > Yeah I can spend hour spliting it, and then people will ignore it
> > anyway.
> >
> > If you care about one of the files being modified, please fix the
> > bug, ";;" is a clear bug.
> >
> > If you don't care ... well I don't care either.
>
> Look, if this causes just one conflict down the line because it touches
> the kernel all over the place, then IMO it already wasn't worth
> it. Merge conflicts are inevitable, but there's no reason to make life
> harder just to cater for a cleanup patch. It's not that important.
>
> Had it been split up, the drm parts would've been merged already.
I just stage patches like this behind linux-next. So if your stuff in
in -next, you'll never notice a thing.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-20 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180217211955.GE9640@amd>
2018-02-18 10:00 ` [PATCH] fix double ;;s in code Christophe LEROY
2018-02-19 15:41 ` Daniel Vetter
2018-02-19 19:33 ` Pavel Machek
[not found] ` <20180219193312.GA3709@amd>
2018-02-20 1:25 ` Rob Clark
[not found] ` <87o9kkcck3.fsf@intel.com>
2018-02-20 16:34 ` Alex Deucher
2018-02-20 23:47 ` Andrew Morton [this message]
[not found] ` <20180219154135.GV22199-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-02-20 6:19 ` Michael Ellerman
2018-02-20 16:41 ` Joe Perches
2018-02-22 9:09 ` Shawn Guo
2018-02-24 8:52 ` Pavel Machek
2018-02-24 8:56 ` Shawn Guo
2018-02-17 21:19 Pavel Machek
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=20180220154715.2a8ecd75a1c2cc698baefd26@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Ding.Wang@amd.com \
--cc=JinHuiEric.Huang@amd.com \
--cc=Rex.Zhu@amd.com \
--cc=Wenjing.Liu@amd.com \
--cc=aik@ozlabs.ru \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alistair@popple.id.au \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andresx7@gmail.com \
--cc=axboe@kernel.dk \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=elfring@users.sourceforge.net \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=narmstrong@baylibre.com \
--cc=oleg@redhat.com \
--cc=paulus@ozlabs.org \
--cc=pavel@ucw.cz \
--cc=ruscur@russell.cc \
--cc=scott.bauer@intel.com \
--cc=shli@kernel.org \
--cc=vbabka@suse.cz \
--cc=viresh.kumar@linaro.org \
--cc=wens@csie.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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