public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Josh Law" <hlcj1234567@gmail.com>,
	"Ethan Tidmore" <ethantidmore06@gmail.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	<linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	"Josh Law" <objecting@objecting.org>
Subject: Re: [PATCH 1/3] staging: axis-fifo: simplify resource mapping
Date: Mon, 02 Mar 2026 15:38:12 -0600	[thread overview]
Message-ID: <DGSMDKT7X2TZ.1IYKDDVKHMYIB@gmail.com> (raw)
In-Reply-To: <0e6cda63-aa40-42c9-92ef-ce1fe177ba0e@gmail.com>

On Mon Mar 2, 2026 at 3:36 PM CST, Josh Law wrote:
> 2 Mar 2026 21:31:31 Ethan Tidmore <ethantidmore06@gmail.com>:
>
>> On Sat Feb 28, 2026 at 6:55 PM CST, Josh Law wrote:
>>> Use devm_platform_ioremap_resource() to simplify the code and remove the unused struct resource pointer.
>>>
>>> Signed-off-by: Josh Law <objecting@objecting.org>
>>> ---
>>
>> I've already told you your patches will *not* be accepted if your from:
>> and SOB do not match, there is actually legal precedent.
>>
>> Thanks,
>>
>> ET
>
> Man.... Check my V2 patches, they are all fixed, Please..

Sorry about that, just realized this is the old. Dan's message made this
pop up.

Thanks,

Et

  reply	other threads:[~2026-03-02 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  0:55 [PATCH 1/3] staging: axis-fifo: simplify resource mapping Josh Law
2026-03-01  0:55 ` [PATCH 2/3] staging: axis-fifo: use dev_err_probe() for IRQ error handling Josh Law
2026-03-01  0:55 ` [PATCH 3/3] staging: axis-fifo: improve IRQ handler Josh Law
2026-03-02  9:19 ` [PATCH 1/3] staging: axis-fifo: simplify resource mapping Dan Carpenter
2026-03-02 21:31 ` Ethan Tidmore
2026-03-02 21:36   ` Josh Law
2026-03-02 21:38     ` Ethan Tidmore [this message]
2026-03-02 21:40       ` Josh Law

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=DGSMDKT7X2TZ.1IYKDDVKHMYIB@gmail.com \
    --to=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hlcj1234567@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=objecting@objecting.org \
    /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