From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Helge Deller <deller@gmx•de>
Cc: Parisc List <linux-parisc@vger•kernel.org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: strange commit in the parisc-hd tree
Date: Tue, 12 Jan 2016 09:32:57 +1100 [thread overview]
Message-ID: <20160112093257.015545ec@canb.auug.org.au> (raw)
In-Reply-To: <569422C8.4000706@gmx.de>
Hi Helge,
On Mon, 11 Jan 2016 22:46:48 +0100 Helge Deller <deller@gmx•de> wrote:
>
> On 10.01.2016 23:28, Stephen Rothwell wrote:
> > I noticed the following commit in the parisc-hd tree today:
> >
> > 43122681dd75 ("Fix __ARCH_SI_PREAMBLE_SIZE on parisc")
> >
> > which among other things says:
> >
> > This patch is not planned to be committed as it currently is.
>
> Right, I split it up into two.
Good idea.
> > [...] Please remove it from linux-next inclusion until it is ready.
>
> Sure, I just removed it now.
Thanks.
> > Delibeately introducing a patch to linux-next that may well cause build breakage
> > in other architectures just before the merge window opens is a bit antisocial.
>
> That was in no way my intention.
> In contrary, I wanted to see if other platforms are affected by the same bug without knowing.
> Do you by any chance know if it broke some of the existing platforms?
> If yes, that would be valuable info...
No, because I took it out of linux-next yesterday. It is more a timing
thing, if you had done that a few weeks ago, I would have just reported
any build errors and continued on, but just before the merge window
opens we don;t need the distraction. Also, if you can create another
branch and give it to the zero day build farm, you should get better
feed back.
Also, linux-next is not supposed to contain patches without a
Signed-off-by ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next prev parent reply other threads:[~2016-01-11 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 22:28 linux-next: strange commit in the parisc-hd tree Stephen Rothwell
2016-01-11 21:46 ` Helge Deller
2016-01-11 22:32 ` Stephen Rothwell [this message]
2016-01-11 22:39 ` Michael Ellerman
2016-01-12 21:43 ` Helge Deller
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=20160112093257.015545ec@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=deller@gmx$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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