From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org
Subject: linux-next: manual merge of the driver-core.current tree
Date: Mon, 20 Oct 2008 11:48:42 +1100 [thread overview]
Message-ID: <20081020114842.e6cd6f90.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Hi Greg,
Today's linux-next merge of the driver-core.current tree got a conflict
in Documentation/sysctl/kernel.txt between commit
061b1bd394ca8628b7c24eb4658ba3535da4249a ("Staging: add TAINT_CRAP for
all drivers/staging code") from Linus' tree and commit
ac7b643ad9c570efa0b5cbc9af5581db8c2faf64 ("Document kernel taint flags
properly") from the driver-core.current tree.
So the Documentation patch in the former commit was not right (64 v 1024
for TAINT_CRAP) ...
I took the latter.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-10-20 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 0:48 Stephen Rothwell [this message]
2008-10-20 3:47 ` linux-next: manual merge of the driver-core.current tree Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-07-24 0:57 Stephen Rothwell
2008-07-24 15:09 ` 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:
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=20081020114842.e6cd6f90.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.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