* linux-next: Fixes tag needs some work in the iomap tree
@ 2019-10-20 20:40 Stephen Rothwell
0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2019-10-20 20:40 UTC (permalink / raw)
To: Darrick J. Wong
Cc: Linux Next Mailing List, Linux Kernel Mailing List, Dave Chinner,
Christoph Hellwig
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
Hi all,
In commit
8a23414ee345 ("iomap: iomap that extends beyond EOF should be marked dirty")
Fixes tag
Fixes: commit 3460cac1ca76 ("iomap: Use FUA for pure data O_DSYNC DIO writes")
has these problem(s):
- leading word 'commit' unexpected
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-20 20:40 linux-next: Fixes tag needs some work in the iomap tree Stephen Rothwell
Linux-Next Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
linux-next@vger.kernel.org
public-inbox-index linux-next
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git