From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: linux-next: Tree for May 15 (drivers/macintosh/ams/ams-core.c)
Date: Mon, 15 May 2023 19:26:53 -0700 [thread overview]
Message-ID: <f9e201cb-71b9-ee38-5fa6-e96dd98cd1a9@infradead.org> (raw)
In-Reply-To: <20230515141235.0777c631@canb.auug.org.au>
On 5/14/23 21:12, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230512:
>
../drivers/macintosh/ams/ams-core.c: In function 'ams_init':
../drivers/macintosh/ams/ams-core.c:181:29: warning: unused variable 'np' [-Wunused-variable]
181 | struct device_node *np;
| ^~
--
~Randy
next prev parent reply other threads:[~2023-05-16 2:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 4:12 linux-next: Tree for May 15 Stephen Rothwell
2023-05-16 2:18 ` linux-next: Tree for May 15 (drivers/dma/ti/k3-udma.c) Randy Dunlap
2023-05-16 17:35 ` Vinod Koul
2023-05-16 2:23 ` linux-next: Tree for May 15 (net/ipv4/ipconfig.c:) Randy Dunlap
2023-05-18 3:57 ` David Ahern
2023-05-16 2:26 ` Randy Dunlap [this message]
2023-05-16 2:40 ` linux-next: Tree for May 15 (drivers/tty/serial/8250/8250_omap.c) Randy Dunlap
2023-05-17 5:51 ` Tony Lindgren
2023-05-16 2:45 ` linux-next: Tree for May 15 (several RV64 build errors) Randy Dunlap
2023-05-16 6:18 ` Alexandre Ghiti
2023-05-19 10:42 ` Alexandre Ghiti
2023-05-19 11:22 ` Conor Dooley
2023-05-19 12:09 ` Alexandre Ghiti
2023-05-23 2:28 ` Randy Dunlap
2023-05-23 13:07 ` Alexandre Ghiti
2023-05-24 0:22 ` Randy Dunlap
2023-05-24 1:29 ` Palmer Dabbelt
2023-05-24 6:23 ` Arnd Bergmann
2023-05-24 22:41 ` Randy Dunlap
2023-05-24 22:49 ` Conor Dooley
2023-05-24 23:11 ` Palmer Dabbelt
2023-05-25 12:50 ` Conor Dooley
2023-05-16 2:51 ` linux-next: Tree for May 15 (config SERIAL_CPM) Randy Dunlap
2023-05-18 5:49 ` Jiri Slaby
2023-05-18 5:50 ` Jiri Slaby
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=f9e201cb-71b9-ee38-5fa6-e96dd98cd1a9@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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