From: Steve French <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven French <Steven.French@microsoft.com>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Samuel Cabrero <scabrero@suse.de>,
Francis Laniel <laniel_francis@privacyrequired.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: linux-next: build failure after merge of the net-next tree
Date: Wed, 16 Dec 2020 10:00:59 -0600 [thread overview]
Message-ID: <CAH2r5mt8ZeX1j2doiZOwJQr_gkDACgeR=F5k1fxXpW8eXYvJew@mail.gmail.com> (raw)
In-Reply-To: <20201216210735.2893dd92@canb.auug.org.au>
On Wed, Dec 16, 2020 at 4:08 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Steven,
>
> On Wed, 16 Dec 2020 02:21:26 +0000 Steven French <Steven.French@microsoft.com> wrote:
> >
> > I applied your patch to the tip of my tree (cifs-2.6.git for-next) -
> > hopefully that makes it easier when I sent the PR in a day or two for
> > cifs/smb3 changes.
>
> I think you have just made your tree fail to build as nla_strscpy does
> not exist in your tree ... Just remove that commit and tell Linus about
> the necessary change and he can add it to the merge.
Done. Removed.
--
Thanks,
Steve
prev parent reply other threads:[~2020-12-16 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SN6PR2101MB1069AC2DC98C74F7C2A71EA3E4C59@SN6PR2101MB1069.namprd21.prod.outlook.com>
2020-12-16 10:07 ` [EXTERNAL] Re: linux-next: build failure after merge of the net-next tree Stephen Rothwell
2020-12-16 16:00 ` Steve French [this message]
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='CAH2r5mt8ZeX1j2doiZOwJQr_gkDACgeR=F5k1fxXpW8eXYvJew@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=Steven.French@microsoft.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=laniel_francis@privacyrequired.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=scabrero@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).