From: "Steve French" <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-cifs-client@lists.samba.org, linux-next@vger.kernel.org,
Jeff Layton <jlayton@redhat.com>,
Harvey Harrison <harvey.harrison@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: manual merge of the cifs tree
Date: Tue, 2 Dec 2008 21:40:59 -0600 [thread overview]
Message-ID: <524f69650812021940m58b5af28g50a7d6be0ac68d52@mail.gmail.com> (raw)
In-Reply-To: <20081203135101.cded370f.sfr@canb.auug.org.au>
Sounds like a good idea for you to carry this since the cifs-2.6.git
tree (which includes this) won't be merged until 2.6.29 opens up in a
few weeks
On Tue, Dec 2, 2008 at 8:51 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Steve,
>
> Today's linux-next merge of the cifs tree got a conflict in
> fs/cifs/connect.c between commit be859405487324ed548f1ba11dc949b8230ab991
> ("fs: replace NIPQUAD()") from the net tree and commits
> c14eef12edfa4b495fe9f6e81571759fe720db1d ("cifs: account for IPv6 in
> ses->serverName and clean up netbios name handling") and
> 6f694429f03ea9b9d2e253fdad2fc3b4cb801195 ("cifs: move allocation of new
> TCP_Server_Info into separate function") from the cifs tree.
>
> I fixed it up (see below) and can carry the fix as necessary.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> diff --cc fs/cifs/connect.c
> index 204bd13,3519420..0000000
> --- a/fs/cifs/connect.c
> +++ b/fs/cifs/connect.c
> @@@ -2228,8 -2269,12 +2269,12 @@@ cifs_mount(struct super_block *sb, stru
>
> /* new SMB session uses our srvTcp ref */
> pSesInfo->server = srvTcp;
> - sprintf(pSesInfo->serverName, "%pI4",
> - &sin_server->sin_addr.s_addr);
> + if (srvTcp->addr.sockAddr6.sin6_family == AF_INET6)
> - sprintf(pSesInfo->serverName, NIP6_FMT,
> - NIP6(srvTcp->addr.sockAddr6.sin6_addr));
> ++ sprintf(pSesInfo->serverName, "%pI6",
> ++ &srvTcp->addr.sockAddr6.sin6_addr);
> + else
> - sprintf(pSesInfo->serverName, NIPQUAD_FMT,
> - NIPQUAD(srvTcp->addr.sockAddr.sin_addr.s_addr));
> ++ sprintf(pSesInfo->serverName, "%pI4",
> ++ &srvTcp->addr.sockAddr.sin_addr.s_addr);
>
> write_lock(&cifs_tcp_ses_lock);
> list_add(&pSesInfo->smb_ses_list, &srvTcp->smb_ses_list);
>
--
Thanks,
Steve
next prev parent reply other threads:[~2008-12-03 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 2:51 linux-next: manual merge of the cifs tree Stephen Rothwell
2008-12-03 3:40 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-17 2:42 Stephen Rothwell
2008-11-19 2:32 ` 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=524f69650812021940m58b5af28g50a7d6be0ac68d52@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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