public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Yoshinori Sato <ysato@users•sourceforge.jp>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: bad base of the h8300 tree
Date: Tue, 1 Sep 2015 07:40:33 +1000	[thread overview]
Message-ID: <20150901074033.4282c9c4@canb.auug.org.au> (raw)
In-Reply-To: <20150831074304.0ce16f9f@canb.auug.org.au>

Hi Yoshinori,

On Mon, 31 Aug 2015 07:43:04 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> The h8300 tree today has been based on linux-next.  This cannto work.
> Please rebase this onto Linus' tree (or some other stable base).
> 
> I cannot use your tree in this state, so it will be dropped from
> linux-next until it is fixed.  Also, Linus cannot pull it in this state.

And now your tree conatins lots and lots of very old commits that do
not even have Signed-off-by tags :-(.  The version I have been using
has a HEAD of commit:

99bcfda85f66 "Revert "asm-generic: {get,put}_user ptr argument evaluate only 1 time""

(which, it turns out" also has no Signed-off-by :-()

Maybe you should reset your tree to that and try to move on from there.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

  reply	other threads:[~2015-08-31 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30 21:43 linux-next: bad base of the h8300 tree Stephen Rothwell
2015-08-31 21:40 ` Stephen Rothwell [this message]
2015-09-13 23:54   ` Stephen Rothwell
2015-09-14 23:10     ` Stephen Rothwell
2015-09-14 23:12       ` Stephen Rothwell
2015-10-02  6:11         ` Yoshinori Sato
2015-10-03  4:28           ` Stephen Rothwell
2015-10-14 22:21             ` Stephen Rothwell
2015-10-19 21:57               ` Stephen Rothwell
2015-10-20  4:28                 ` Yoshinori Sato
2015-10-20 20:42                   ` Stephen Rothwell

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=20150901074033.4282c9c4@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ysato@users$(echo .)sourceforge.jp \
    /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