linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesper Nilsson <jespern@axis.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-cris-kernel <linux-cris-kernel@axis.com>
Subject: Re: [GIT PULL]: CRIS changes for 4.4
Date: Tue, 3 Nov 2015 10:18:54 +0100	[thread overview]
Message-ID: <20151103091854.GE22903@axis.com> (raw)
In-Reply-To: <20151103114923.70e246d2@canb.auug.org.au>

On Tue, Nov 03, 2015 at 01:49:23AM +0100, Stephen Rothwell wrote:
> Hi Jesper,
> 
> On Mon, 2 Nov 2015 21:17:03 +0100 Jesper Nilsson <jesper.nilsson@axis.com> wrote:
> >
> > Please pull CRIS changes for 4.4:
> > 
> > Mostly another batch of code removal due to move to standard
> > frameworks for CRISv32, initial devicetree configuration for
> > a couple of boards, and some small fixes for kgdb and time handling.
> > 
> > Thanks,
> > 
> > /Jesper
> > 
> > The following changes since commit 6a13feb9c82803e2b815eca72fa7a9f5561d7861:
> > 
> >   Linux 4.3 (2015-11-01 16:05:25 -0800)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris.git tags/cris-for-4.4
> 
> This is all the same patches as are in linux-next (and have been for
> some time) but has been rebased on top of v4.3 today ...

Yes, you're right, I did do a rebase to make a final
compile test, I should have dropped that branch and
sent the for-next branch instead. :-(

> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

      reply	other threads:[~2015-11-03  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 20:17 [GIT PULL]: CRIS changes for 4.4 Jesper Nilsson
2015-11-03  0:49 ` Stephen Rothwell
2015-11-03  9:18   ` Jesper Nilsson [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=20151103091854.GE22903@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=akpm@linux-foundation.org \
    --cc=jespern@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).