From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Trond Myklebust <trond.myklebust@fys•uio.no>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Anna Schumaker <Anna.Schumaker@Netapp•com>
Subject: linux-next: bad commits in the nfs tree
Date: Wed, 4 Jun 2014 08:34:11 +1000 [thread overview]
Message-ID: <20140604083411.4296bcd5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
Hi Trond,
I noticed in the nfs tree this morning 2 commits that have been
cherry-picked from Linus' tree:
cc6d854967ce Linux 3.15-rc8
2b267bb3a8e5 powerpc: Wire renameat2() syscall
These are part of a branch that you merged from Anna Schumaker. It
looks like they may have been included when Anna was trying to rebase
the rest of the branch onto v3.15-rc8?
Please fix this up before asking Linus to pull your tree.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-06-03 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 22:34 Stephen Rothwell [this message]
2014-06-03 22:46 ` linux-next: bad commits in the nfs tree Trond Myklebust
2014-06-04 12:38 ` Anna Schumaker
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=20140604083411.4296bcd5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Anna.Schumaker@Netapp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=trond.myklebust@fys$(echo .)uio.no \
/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