From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "James E.J. Bottomley" <JBottomley@odin.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] scsi: sim710: fix build warning
Date: Sat, 9 Jan 2016 13:12:06 +0530 [thread overview]
Message-ID: <20160109074206.GA27241@sudip-pc> (raw)
In-Reply-To: <20151209114551.GB24852@sudip-pc>
On Wed, Dec 09, 2015 at 05:15:51PM +0530, Sudip Mukherjee wrote:
> On Tue, Sep 15, 2015 at 01:30:00PM +0530, Sudip Mukherjee wrote:
> > On Fri, Sep 04, 2015 at 07:40:29PM +0530, Sudip Mukherjee wrote:
> > > We were getting build warning about:
> > > "Section mismatch in reference from the variable sim710_eisa_driver to
> > > the function .init.text:sim710_eisa_probe()
> > > The variable sim710_eisa_driver references the function __init
> > > sim710_eisa_probe()"
> > >
> > > sim710_eisa_probe() was having __init but that was being referenced from
> > > sim710_eisa_driver.
> > >
> > > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > > ---
> > A gentle ping.
> > I still get the build warning while building for i386 allmodconfig with
> > next-20150915.
> > Build is at https://travis-ci.org/sudipm-mukherjee/parport/jobs/80365417
>
> Another gentle ping. Build warning with i386 allmodconfig is still there
> with next-20151209.
> Build log is at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/95746184
Another gentle ping. Build warning with i386 allmodconfig is still there
with next-20160108.
Build log is at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/101006139
regards
sudip
prev parent reply other threads:[~2016-01-09 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 14:10 [PATCH] scsi: sim710: fix build warning Sudip Mukherjee
2015-09-15 8:00 ` Sudip Mukherjee
2015-12-09 11:45 ` Sudip Mukherjee
2016-01-09 7:42 ` Sudip Mukherjee [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=20160109074206.GA27241@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=JBottomley@odin.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).