public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Nadia Yvette Chambers <nyc@holomorphy•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Jiri Kosina <jkosina@suse•cz>,
	Andrew Morton <akpm@linux-foundation•org>
Subject: Re: [patch] propagate name change to comments in kernel source
Date: Wed, 05 Dec 2012 20:17:14 -0500	[thread overview]
Message-ID: <1354756634.9720.203.camel@tisifone> (raw)
In-Reply-To: <20121206120148.99919a3512c72947c8baba67@canb.auug.org.au>

On Thu, 2012-12-06 at 12:01 +1100, Stephen Rothwell wrote:
> OK, that may be a problem.  Does this patch apply to Linus' tree
> currently?  I guess not.  So, either you need to split it up and send it
> to the various maintainers (most if it can probably go through the trivial
> tree (cc'd)).  Or wait until after v3.8-rc1 and fix it so it applies to
> Linus' tree and send it to him.
> Or Andrew (cc'd) may be able to take it (as his tree is based on
> linux-next currently).
> (I have attached the patch for Jiri's and Andrew's benefit)

It applies with offsets to Linus' current git, actually. I can provide a
diff applying with no offsets, but suspect it's unnecessary. The
affected comment blocks don't seem to have experienced much turnover
recently, if ever.

-- nyc

  reply	other threads:[~2012-12-06  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06  0:44 [patch] propagate name change to comments in kernel source Nadia Yvette Chambers
2012-12-06  1:01 ` Stephen Rothwell
2012-12-06  1:17   ` Nadia Yvette Chambers [this message]
2012-12-06  9:41     ` Jiri Kosina

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=1354756634.9720.203.camel@tisifone \
    --to=nyc@holomorphy$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=jkosina@suse$(echo .)cz \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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