linux-hexagon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Arnd Bergmann <arnd@kernel.org>, Brian Cain <bcain@quicinc.com>
Cc: "linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>,
	Heiko Carstens <hca@linux.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without HAS_IOPORT support
Date: Wed, 02 Oct 2024 13:54:26 +0200	[thread overview]
Message-ID: <60294f0b70dc1f5f04cd32e43c7c13ccb2ff4374.camel@linux.ibm.com> (raw)
In-Reply-To: <75ea0839-1489-4f49-abcd-104e657a42c5@app.fastmail.com>

On Wed, 2024-10-02 at 09:34 +0000, Arnd Bergmann wrote:
> On Tue, Oct 1, 2024, at 08:04, Niklas Schnelle wrote:
> > On Mon, 2024-09-30 at 16:35 +0000, Brian Cain wrote:
> > > > 
> > > > With 2 more of my HAS_IOPORT patches having gone into v6.12-rc1 I just
> > > > noticed that this one seems to have fallen into the cracks. This is
> > > > probably my fault for not properly confirming that I'd be happy for you
> > > > to take it. Do you want me to resend a new version rebased on v6.12-
> > > > rc1?
> > > 
> > > Oh, sorry!  Yes, if you could resend a rebased one I'll make sure I am able to land it.
> > > 
> > > -Brian
> > 
> > Hi Brian,
> > 
> > I just tried with
> > 
> >    b4 shazam '<20240403132447.719833-2-schnelle@linux.ibm.com>'
> > 
> > and this patch actually still applies cleanly and matches the result I
> > got rebasing the whole series[0]. So on second thought taking it from
> > here directly might still be the easiest. That said I'll have to send
> > out the other 4 outstanding patches required for the final inb()
> > compile time switch, so if you prefer I can still resend too.
> 
> Hi Niklas,
> 
> For simplicity I would suggest you keep all the remaining patches
> as a series now and I'll take them through the asm-generic
> tree in order to get them in more easily along with the final patch.
> 
>       Arnd

Hi Arnd,

Works for me. So, I think apart from this one that was simply missed
and has an Ack the Bluetooth patch hasn't seen any feedback, for the
drm one I have a few minor todos and then there is the tty/serial one.

So maybe I can just sent a version of all the remaining ones and add
all the remaining maintainers for the whole series. I'll include a note
that we plan on taking this through asm-generic.

Thanks,
Niklas

      reply	other threads:[~2024-10-02 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 13:24 [PATCH 0/1] hexagon: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-03 13:24 ` [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without HAS_IOPORT support Niklas Schnelle
2024-04-03 14:51   ` Brian Cain
2024-04-03 15:22     ` Niklas Schnelle
2024-04-03 15:37       ` Brian Cain
2024-09-30 15:50         ` Niklas Schnelle
2024-09-30 16:35           ` Brian Cain
2024-10-01  8:04             ` Niklas Schnelle
2024-10-02  9:34               ` Arnd Bergmann
2024-10-02 11:54                 ` Niklas Schnelle [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=60294f0b70dc1f5f04cd32e43c7c13ccb2ff4374.camel@linux.ibm.com \
    --to=schnelle@linux.ibm.com \
    --cc=arnd@kernel.org \
    --cc=bcain@quicinc.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).