mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [PATCH] parport_pc: Avoid FIFO port location truncation
Date: Mon, 3 Oct 2022 15:58:24 +0200	[thread overview]
Message-ID: <YzrqgInDvNcKHXta@kroah.com> (raw)
In-Reply-To: <CADVatmMBMgk1Uga46FWs4CysiCQ2JQhyfSyp4OK1VDnLdAXSCg@mail.gmail.com>

On Mon, Oct 03, 2022 at 12:19:14PM +0100, Sudip Mukherjee wrote:
> On Fri, Sep 23, 2022 at 7:52 PM Maciej W. Rozycki <macro@orcam.me.uk> wrote:
> >
> > Match the data type of a temporary holding a reference to the FIFO port
> > with the type of the original reference coming from `struct parport',
> > avoiding data truncation with LP64 ports such as SPARC64 that refer to
> > PCI port I/O locations via their corresponding MMIO addresses and will
> > therefore have non-zero bits in the high 32-bit part of the reference.
> > And in any case it is cleaner to have the data types matching here.
> >
> > Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Link: https://lore.kernel.org/linux-pci/20220419033752.GA1101844@bhelgaas/
> 
> Thanks for the patch Maciej.
> 
> Acked-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> 
> Greg, can you please add it to your tree. I know I am late and the
> merge window is now open.

Will have to wait until 6.1-rc1 is out, I'll take it then, thanks.

greg k-h

      reply	other threads:[~2022-10-03 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 18:52 Maciej W. Rozycki
2022-10-03 11:19 ` Sudip Mukherjee
2022-10-03 13:58   ` Greg Kroah-Hartman [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=YzrqgInDvNcKHXta@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=sudipm.mukherjee@gmail.com \
    /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®