From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Tilman Schmidt <tilman@imap•cc>,
Jesse Barnes <jbarnes@virtuousgeek•org>
Subject: Re: linux-next: Tree for January 21
Date: Thu, 21 Jan 2010 13:13:39 -0800 [thread overview]
Message-ID: <20100121131339.5e86dfef.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100121165713.7b8a746d.sfr@canb.auug.org.au>
On Thu, 21 Jan 2010 16:57:13 +1100
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
It includes this screwed up commit:
:commit e303d9eadc64907535a0a104afa5871d2b83275e
:Author: Tilman Schmidt <tilman@imap•cc>
:AuthorDate: Thu Jan 14 23:18:41 2010 +0100
:Commit: Jesse Barnes <jbarnes@virtuousgeek•org>
:CommitDate: Fri Jan 15 10:08:07 2010 -0800
:
: PCI/ISDN: push deprecated pci_find_device() function to last user (isdn)
:
: The ISDN4Linux HiSax driver family contains the last remaining users of
: the deprecated pci_find_device() function. This patch creates a private
: copy of that function in HiSax, and removes the now unused global
: function together with its controlling configuration option,
: CONFIG_PCI_LEGACY.
:
: Signed-off-by: Tilman Schmidt <tilman@imap•cc>
: Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek•org>
It adds a bunch of files which are compile-time generated:
include/linux/autoconf.h
include/linux/bounds.h
include/linux/compile.h
include/linux/utsrelease.h
next prev parent reply other threads:[~2010-01-21 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 5:57 linux-next: Tree for January 21 Stephen Rothwell
2010-01-21 21:13 ` Andrew Morton [this message]
2010-01-21 23:00 ` Tilman Schmidt
2010-01-22 1:31 ` Jesse Barnes
2010-01-25 18:47 ` Jesse Barnes
2010-01-21 23:00 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-01-21 2:27 Stephen Rothwell
2009-01-21 4:02 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=20100121131339.5e86dfef.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tilman@imap$(echo .)cc \
/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