mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Povišer" <povik+lin@cutebit.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	dmaengine@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 15 (drivers/dma/apple-admac.c)
Date: Wed, 15 Jun 2022 19:23:37 +0200	[thread overview]
Message-ID: <334755C8-8FF2-49D3-ACC3-C76F3BCCBB4F@cutebit.org> (raw)
In-Reply-To: <CAK8P3a2mQiWKyVux+bfAJiRH=72q76UTLZnBbPCLVFVoXpGfaw@mail.gmail.com>


> On 15. 6. 2022, at 19:10, Arnd Bergmann <arnd@arndb.de> wrote:
> 
> On Wed, Jun 15, 2022 at 6:28 PM Randy Dunlap <rdunlap@infradead.org> wrote:

>> On 6/14/22 23:01, Stephen Rothwell wrote:
>>> Hi all,
>>> 
>>> Changes since 20220614:
>>> 
>> 
>> on i386:
>> 
>> ../drivers/dma/apple-admac.c: In function 'admac_cyclic_write_one_desc':
>> ../drivers/dma/apple-admac.c:213:22: warning: right shift count >= width of type [-Wshift-count-overflow]
>>  writel_relaxed(addr >> 32,       ad->base + REG_DESC_WRITE(channo));
>>                      ^
> 
> This should probably use lower_32_bits()/upper_32_bits() then.
> 
>       Arnd

Here’s a patch to use lower/upper_32_bits that’s been posted.

https://lore.kernel.org/dmaengine/20220614074915.1443629-1-geert@linux-m68k.org/

Martin


  reply	other threads:[~2022-06-15 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  6:01 linux-next: Tree for Jun 15 Stephen Rothwell
2022-06-15 16:28 ` linux-next: Tree for Jun 15 (drivers/dma/apple-admac.c) Randy Dunlap
2022-06-15 17:10   ` Arnd Bergmann
2022-06-15 17:23     ` Martin Povišer [this message]
2022-06-15 19:01 ` linux-next: Tree for Jun 15 (drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c) Randy Dunlap
2022-06-15 19:28   ` Alex Deucher
2022-06-15 19:44     ` Randy Dunlap
2022-06-15 20:13       ` Alex Deucher
2022-06-15 20:27         ` Randy Dunlap
2022-06-15 20:24     ` Nathan Chancellor
2022-06-15 20:45       ` Alex Deucher
2022-06-15 20:52         ` Nathan Chancellor
2022-06-15 23:26           ` Stephen Rothwell
2022-06-16  2:34             ` Alex Deucher

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=334755C8-8FF2-49D3-ACC3-C76F3BCCBB4F@cutebit.org \
    --to=povik+lin@cutebit.org \
    --cc=arnd@arndb.de \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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
all inboxes | Powered by JetHome®