From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kbuild test robot <lkp@intel.com>, Olliver Schinagl <oliver@schinagl.nl>
Cc: kbuild-all@01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
dev@linux-sunxi.org, Ed Blake <ed.blake@imgtec.com>,
Alexander Sverdlin <alexander.sverdlin@nokia.com>,
Yegor Yefremov <yegorslists@googlemail.com>,
Wan Ahmad Zainie <wan.ahmad.zainie.wan.mohamad@intel.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Heiko Stuebner <heiko@sntech.de>,
Jason Uy <jason.uy@broadcom.com>,
Douglas Anderson <dianders@chromium.org>,
Peter Hurley <peter@hurleysoftware.com>,
Tony Lindgren <tony@atomide.com>, Vignesh R <vigneshr@ti.com>,
Thor Thayer <tthayer@opensource.altera.com>,
David Lechner <david@lechnology.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH] serial: Do not treat the IIR register as a bitfield
Date: Thu, 30 Mar 2017 13:32:51 +0300 [thread overview]
Message-ID: <1490869971.708.66.camel@linux.intel.com> (raw)
In-Reply-To: <201703301843.OZzxWtxO%fengguang.wu@intel.com>
On Thu, 2017-03-30 at 18:22 +0800, kbuild test robot wrote:
> drivers/net//irda/smsc-ircc2.c:
> > > drivers/net//irda/smsc-ircc2.c:
Just out of my curiosity, why do we have // in some reports?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-30 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:44 [PATCH] serial: Do not treat the IIR register as a bitfield Olliver Schinagl
2017-03-30 6:15 ` Vignesh R
2017-03-30 6:43 ` Olliver Schinagl
2017-03-30 7:57 ` Vignesh R
2017-03-30 15:39 ` Olliver Schinagl
2017-03-30 14:11 ` Theodore Ts'o
2017-03-31 11:28 ` Olliver Schinagl
2017-03-30 9:56 ` Andy Shevchenko
2017-03-31 13:54 ` Olliver Schinagl
2017-03-31 14:44 ` Andy Shevchenko
2017-03-30 10:06 ` kbuild test robot
2017-03-30 10:22 ` kbuild test robot
2017-03-30 10:32 ` Andy Shevchenko [this message]
2017-03-30 11:27 ` [kbuild-all] " Fengguang Wu
2017-03-30 12:18 ` kbuild test robot
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=1490869971.708.66.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexander.sverdlin@nokia.com \
--cc=davem@davemloft.net \
--cc=david@lechnology.com \
--cc=dev@linux-sunxi.org \
--cc=dianders@chromium.org \
--cc=ed.blake@imgtec.com \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko@sntech.de \
--cc=jan.kiszka@siemens.com \
--cc=jason.uy@broadcom.com \
--cc=jslaby@suse.com \
--cc=kbuild-all@01.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oliver@schinagl.nl \
--cc=peter@hurleysoftware.com \
--cc=sparclinux@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=tthayer@opensource.altera.com \
--cc=vigneshr@ti.com \
--cc=wan.ahmad.zainie.wan.mohamad@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yegorslists@googlemail.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