From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
David Howells <dhowells@redhat•com>,
Steve French <smfrench@gmail•com>,
linux-cifs@vger•kernel.org
Subject: linux-next: manual merge of the workqueues tree with the Linus' tree
Date: Fri, 23 Jul 2010 14:46:00 +1000 [thread overview]
Message-ID: <20100723144600.dd4da992.sfr@canb.auug.org.au> (raw)
Hi Tejun,
Today's linux-next merge of the workqueues tree got a conflict in
fs/cifs/cifsfs.c between commit 4c0c03ca54f72fdd5912516ad0a23ec5cf01bda7
("CIFS: Fix a malicious redirect problem in the DNS lookup code") from
Linus' tree and commit 9b646972467fb5fdc677f9e4251875db20bdbb64 ("cifs:
use workqueue instead of slow-work") from the workqueues tree.
I fixed it up (I think - I removed the call to cifs_exit_dns_resolver()
as there is no way to get to that code any more) and can carry the fix
for a while.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next reply other threads:[~2010-07-23 4:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 4:46 Stephen Rothwell [this message]
[not found] ` <20100723144600.dd4da992.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-07-23 11:28 ` linux-next: manual merge of the workqueues tree with the Linus' tree Tejun Heo
[not found] ` <4C497CD5.5010908-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2010-07-23 11:31 ` Stephen Rothwell
[not found] ` <20100723213148.3d2193a3.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-07-23 11:34 ` Tejun Heo
[not found] ` <4C497E5F.80301-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2010-07-23 11:42 ` Stephen Rothwell
[not found] ` <20100723214233.7cb7de8d.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-07-23 11:45 ` Tejun Heo
2010-08-05 3:04 ` Stephen Rothwell
2010-08-05 3:45 ` Stephen Rothwell
2010-07-23 12:05 ` David Howells
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=20100723144600.dd4da992.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-cifs@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=smfrench@gmail$(echo .)com \
--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