mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jiri Kosina <jikos@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] trivial for 4.10
Date: Wed, 14 Dec 2016 06:23:00 -0800	[thread overview]
Message-ID: <1481725380.29291.52.camel@perches.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1612141040590.16984@cbobk.fhfr.pm>

On Wed, 2016-12-14 at 11:05 +0100, Jiri Kosina wrote:
> Linus,
> 
> please pull from
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git for-linus
> 
> to receive 4.10 merge window updates from trivial tree
> 
> I hereby confess to having rebased the for-next branch, because I wanted 
> to drop all the '\n' additions that were obsoleted by the recent printk / 
> pr_cont changes, and didn't want to pollute the history with unnecessary 
> commit+revert for such a triviality; as a consequence, you're getting 
> different commit hashes for the 5 commits compared to what's in 
> linux-next; I believe it's fine for such a insignificant tree / commits.
> 

I'd rather have the dozen or so single-line newline additions
than the multiple hundreds to thousands of changes that are
still going to be required to get KERN_CONT to work properly
kernel-wide.

Many arch specific printks still have to be fixed for this
new KERN_CONT style.  sparc, powerpc, arm, arm64, and others.

Multiple dozens to hundreds of drivers too.

      reply	other threads:[~2016-12-14 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 10:05 Jiri Kosina
2016-12-14 14:23 ` Joe Perches [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=1481725380.29291.52.camel@perches.com \
    --to=joe@perches.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®