mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Artur Rojek <contact@artur-rojek.eu>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	Rafael Ignacio Zurita <rafaelignacio.zurita@gmail.com>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] sh: dma: fix `dmaor_read_reg`/`dmaor_write_reg` macros
Date: Sat, 13 May 2023 17:02:09 +0200	[thread overview]
Message-ID: <6977d52a797af5dfa3a863ac32bee8a9553bf86a.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <0ea0b05e99f63edf05ef9a0afe410fc1@artur-rojek.eu>

Hi Artur!

On Sat, 2023-05-13 at 16:57 +0200, Artur Rojek wrote:
> > Maybe you're also interested in the clean-up that Geert suggested in 
> > this
> > thread (ordering of the CPU subtypes and capitalization issues)?
> 
> Sure, why not - the more clean-up we do, the better :)

Great, thanks a lot!

> > Also, can you write "processor manual" instead of "PM" in the other 
> > patch
> > as well as don't use backticks for the macro names? In fact, I would 
> > suggest
> > retitling the subject to:
> > 
> > 	sh: dma: Fix dmaor_read_reg() and dmaor_write_reg() macros
> > 
> 
> Of course.
> On a side note, it was supposed to be "programming manual", however I
> now see that Renesas named that document as "hardware manual", so that's
> what I'll put into the commit description, if you don't mind.

Absolutely not! Looking forward to your v2 series and please take your time!

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-05-13 15:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 14:17 [PATCH 0/2] SH7709 DMA fixes Artur Rojek
2023-05-06 14:17 ` [PATCH 1/2] sh: dma: fix `dmaor_read_reg`/`dmaor_write_reg` macros Artur Rojek
2023-05-07  8:39   ` John Paul Adrian Glaubitz
2023-05-07  9:34     ` Artur Rojek
2023-05-07 10:32       ` John Paul Adrian Glaubitz
2023-05-11 20:11         ` John Paul Adrian Glaubitz
2023-05-08 11:20       ` Geert Uytterhoeven
2023-05-08 11:27         ` John Paul Adrian Glaubitz
2023-05-08 11:46           ` Geert Uytterhoeven
2023-05-13 11:41         ` Artur Rojek
2023-05-13 14:45           ` John Paul Adrian Glaubitz
2023-05-13 14:57             ` Artur Rojek
2023-05-13 15:02               ` John Paul Adrian Glaubitz [this message]
2023-05-10  6:25   ` John Paul Adrian Glaubitz
2023-05-06 14:17 ` [PATCH 2/2] sh: dma: Correct the number of DMA channels in SH7709 Artur Rojek
2023-05-07  8:33   ` John Paul Adrian Glaubitz
2023-05-08 10:55   ` Geert Uytterhoeven
2023-05-11 20:20     ` John Paul Adrian Glaubitz
2023-05-12  7:34       ` Geert Uytterhoeven
2023-05-12  8:43         ` John Paul Adrian Glaubitz
2023-05-06 15:25 ` [PATCH 0/2] SH7709 DMA fixes John Paul Adrian Glaubitz
2023-05-06 16:56   ` Rich Felker
2023-05-11 20:12     ` John Paul Adrian Glaubitz
2023-07-06  6:34 ` John Paul Adrian Glaubitz

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=6977d52a797af5dfa3a863ac32bee8a9553bf86a.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=contact@artur-rojek.eu \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rafaelignacio.zurita@gmail.com \
    --cc=ysato@users.sourceforge.jp \
    /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®