archive mirror
 help / color / mirror / Atom feed
From: Greg KH <>
To: Linus Torvalds <>,
	Andrew Morton <>
Cc:, Junio C Hamano <>
Subject: [GIT PATCH] driver core patches for 3.3-rc1
Date: Fri, 27 Jan 2012 15:09:46 -0800	[thread overview]
Message-ID: <> (raw)

I tried to create a signed tag for this pull request.  It's call
"driver-core-3.3-rc1-bugfixes" in the repo below, but when I did:
    git request-pull master git:// driver-core-3.3-rc1-bugfixes > msg.txt

I got the text below, no signed tag with the wording that I added to it
that I could see.  Now I am still using git, is that why?  If
so, I'll go build 1.7.9 as I see that is now out today.

Did I mess something up?  I created the tag with:
    git tag -u -s driver-core-3.3-rc1-bugfixes driver-core-linus

Could it be that the tag and the branch are at the same point in the
tree right now?  Or something else?

The wording I put in the tag is:
	Here are some patches for the 3.3-rc1 tree.

	It contains the removal of the sysdev code, now that all users
	of it are gone, as well as some sysfs bugfixes that have been
	reported by users.  There are also some documentation updates
	here as well.

All of these have been in the linux-next tree for the past week.


greg k-h


The following changes since commit dcd6c92267155e70a94b3927bce681ce74b80d1f:

  Linux 3.3-rc1 (2012-01-19 15:04:48 -0800)

are available in the git repository at:
  git:// driver-core-linus

Alan Stern (1):
      Documentation update for the driver model core

Eric W. Biederman (1):
      sysfs: Complain bitterly about attempts to remove files from nonexistent directories.

Greg Kroah-Hartman (2):
      driver core: remove drivers/base/sys.c and include/linux/sysdev.h
      stable: update documentation to ask for kernel version

Randy Dunlap (3):
      kernel-doc: fix new warnings in device.h
      kernel-doc: fix new warnings in debugfs
      kernel-doc: fix new warnings in driver-core

Wolfram Sang (1):
      Documentation: devres: add allocation functions to list of supported calls

majianpeng (1):
      base/core.c:fix typo in comment in function device_add

 Documentation/driver-model/devres.txt |    4 +
 Documentation/stable_kernel_rules.txt |    3 +-
 drivers/base/Makefile                 |    2 +-
 drivers/base/bus.c                    |    9 +-
 drivers/base/core.c                   |   17 ++-
 drivers/base/sys.c                    |  383 ---------------------------------
 fs/debugfs/file.c                     |    2 +-
 fs/sysfs/file.c                       |    6 +
 fs/sysfs/inode.c                      |    5 +-
 include/linux/device.h                |   15 +-
 include/linux/sysdev.h                |  164 --------------
 11 files changed, 49 insertions(+), 561 deletions(-)
 delete mode 100644 drivers/base/sys.c
 delete mode 100644 include/linux/sysdev.h

             reply	other threads:[~2012-01-27 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 23:09 Greg KH [this message]
2012-01-28  8:34 ` [GIT PATCH] driver core patches for 3.3-rc1 Junio C Hamano
2012-01-30 21:15   ` Greg KH
2012-01-29  2:22 ` Linus Torvalds
2012-01-30 21:14   ` Greg KH

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).