mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Law <hlcj1234567@gmail.com>
To: 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, 2 Mar 2026 21:40:24 +0000	[thread overview]
Message-ID: <031d4c2e-1bac-4cab-a9a3-837a794b481f@gmail.com> (raw)
In-Reply-To: <DGSMDKT7X2TZ.1IYKDDVKHMYIB@gmail.com>

2 Mar 2026 21:38:35 Ethan Tidmore <ethantidmore06@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

Well, at least one has to be merged haha, I think 2-3 has issues (according to Dan), but I will fix those tomorrow

Thanks

V/R

Josh law

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  0:55 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
2026-03-02 21:40       ` Josh Law [this message]

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=031d4c2e-1bac-4cab-a9a3-837a794b481f@gmail.com \
    --to=hlcj1234567@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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
all inboxes | Powered by JetHome®