From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Helge Deller <deller@gmx•de>, Parisc List <linux-parisc@vger•kernel.org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: strange commit in the parisc-hd tree
Date: Mon, 11 Jan 2016 09:28:22 +1100 [thread overview]
Message-ID: <20160111092822.4b4c0233@canb.auug.org.au> (raw)
Hi all,
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.
It also has no Signed-off-by :-(
Please remove it from linux-next inclusion until it is ready. 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.
I will merge a revert commit for it today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next reply other threads:[~2016-01-10 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 22:28 Stephen Rothwell [this message]
2016-01-11 21:46 ` linux-next: strange commit in the parisc-hd tree Helge Deller
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=20160111092822.4b4c0233@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