public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver•com>
To: Tejun Heo <tj@kernel•org>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Bogus dir.c file introduced at top level.
Date: Wed, 19 Feb 2014 13:02:16 -0500	[thread overview]
Message-ID: <5304F1A8.1030503@windriver.com> (raw)

Hi Tiejun,

This merge:

commit a8fa94e0f2ab665f9aa665195618178b61ed8304
Merge: 9561a89 b28a960
Author: Tejun Heo <tj@kernel•org>
Date:   Mon Feb 10 19:34:30 2014 -0500

    Merge branch 'master' into driver-core-next-test-merge-rc2

introduces a bogus copy of fs/kernfs/dir.c at the top level of
the tree.  Seen in the Feb19th linux-next tree.

Thanks,
Paul.

             reply	other threads:[~2014-02-19 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 18:02 Paul Gortmaker [this message]
2014-02-19 18:25 ` Bogus dir.c file introduced at top level Tejun Heo
2014-02-19 18:29   ` [PATCH driver-core-next] kernfs: remove duplicate dir.c at the top dir Tejun Heo

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=5304F1A8.1030503@windriver.com \
    --to=paul.gortmaker@windriver$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tj@kernel$(echo .)org \
    /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