From: Sergei Shtylyov <sergei.shtylyov@gmail.com> To: Christoph Hellwig <hch@lst.de>, axboe@kernel.dk Cc: torvalds@linux-foundation.org, linux-ide@vger.kernel.org, kernel test robot <oliver.sang@intel.com> Subject: Re: [PATCH] libata: fix ata_pio_sector for CONFIG_HIGHMEM Date: Thu, 5 Aug 2021 21:28:15 +0300 [thread overview] Message-ID: <27f1ac93-1a8b-0b90-7fe2-aeb19c91c8ce@gmail.com> (raw) In-Reply-To: <20210709130237.3730959-1-hch@lst.de> Hello! On 7/9/21 4:02 PM, Christoph Hellwig wrote: > Data transfers are not required to be block aligned in memory, so they > span two pages. Fix this by splitting the call to >sff_data_xfer into > two for that case. > > This has been broken since the initial libata import before the damn > of git, but was uncovered by the legacy ide driver removal. Damn of git, hehe... :-) > Reported-by: kernel test robot <oliver.sang@intel.com> > Signed-off-by: Christoph Hellwig <hch@lst.de> [...] MBR, Sergei
prev parent reply other threads:[~2021-08-05 18:28 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-09 13:02 Christoph Hellwig 2021-07-09 14:28 ` Jens Axboe 2021-08-05 18:28 ` Sergei Shtylyov [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=27f1ac93-1a8b-0b90-7fe2-aeb19c91c8ce@gmail.com \ --to=sergei.shtylyov@gmail.com \ --cc=axboe@kernel.dk \ --cc=hch@lst.de \ --cc=linux-ide@vger.kernel.org \ --cc=oliver.sang@intel.com \ --cc=torvalds@linux-foundation.org \ --subject='Re: [PATCH] libata: fix ata_pio_sector for CONFIG_HIGHMEM' \ /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
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).