linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Shyam Prasad <Shyam.Prasad@microsoft.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"samba-technical@lists.samba.org"
	<samba-technical@lists.samba.org>,
	"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
	Maciek Borzecki <maciek.borzecki@gmail.com>,
	Wan Jiabing <wanjiabing@vivo.com>,
	Steven French <Steven.French@microsoft.com>, pc <pc@cjr.nz>,
	Pavel Shilovskiy <pshilov@microsoft.com>,
	Steve French <sfrench@samba.org>
Subject: Re: [EXTERNAL] [next] ERROR: modpost: "dns_query" [fs/cifs/cifs.ko] undefined
Date: Fri, 9 Apr 2021 23:24:14 +0530	[thread overview]
Message-ID: <CA+G9fYuNHTscCZDwGnxv5axibgUw1iRKQ4RJrJxHQpSNrQPaBg@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYvcSK-Z7+VrRbHp7ADDDgw2tWWaqTfQMyC2dxuOYGLz6A@mail.gmail.com>

On Fri, 9 Apr 2021 at 23:17, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> On Fri, 9 Apr 2021 at 21:49, Shyam Prasad <Shyam.Prasad@microsoft.com> wrote:
> >
> > Hi Naresh,
> >
> > AFAIK, this has been fixed in an updated patch last evening. Can you please check if you're still seeing it?
>
> Please share the fix commit and subject here.
>
> FYI,

ignore the below statement.
our build system did not trigger today tag yet.

> This build error is still on today's Linux next tag 20210409.

- Naresh

  reply	other threads:[~2021-04-09 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  5:06 [next] ERROR: modpost: "dns_query" [fs/cifs/cifs.ko] undefined Naresh Kamboju
2021-04-09 16:19 ` [EXTERNAL] " Shyam Prasad
2021-04-09 17:47   ` Naresh Kamboju
2021-04-09 17:54     ` Naresh Kamboju [this message]
2021-04-09 17:57       ` Shyam Prasad

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=CA+G9fYuNHTscCZDwGnxv5axibgUw1iRKQ4RJrJxHQpSNrQPaBg@mail.gmail.com \
    --to=naresh.kamboju@linaro.org \
    --cc=Shyam.Prasad@microsoft.com \
    --cc=Steven.French@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=maciek.borzecki@gmail.com \
    --cc=pc@cjr.nz \
    --cc=pshilov@microsoft.com \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=wanjiabing@vivo.com \
    /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).