linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Parisc List <linux-parisc@vger.kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: strange commit in the parisc-hd tree
Date: Mon, 11 Jan 2016 22:46:48 +0100	[thread overview]
Message-ID: <569422C8.4000706@gmx.de> (raw)
In-Reply-To: <20160111092822.4b4c0233@canb.auug.org.au>

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.

> [...] Please remove it from linux-next inclusion until it is ready.

Sure, I just removed it now.

> 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...

Just in case people want to know what this is all about:
On parisc I found __ARCH_SI_PREAMBLE_SIZE to have a wrong value in 64bit kernel builds.
Patch which fixes it is here:
https://patchwork.kernel.org/patch/7994821/

To prevent other (existing and future) architectures to run into the same
problem I wanted to test this patch via linux-next and inform them:
http://git.kernel.org/cgit/linux/kernel/git/deller/parisc-linux.git/commit/?h=test__ARCH_SI_PREAMBLE_SIZE

Helge

  reply	other threads:[~2016-01-11 21:46 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 [this message]
2016-01-11 22:32   ` Stephen Rothwell
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=569422C8.4000706@gmx.de \
    --to=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).