From: Dan Williams <email@example.com> To: Ingo Molnar <firstname.lastname@example.org> Cc: linux-nvdimm <email@example.com>, "Luck, Tony" <firstname.lastname@example.org>, "Andrew Morton" <email@example.com>, "Mike Snitzer" <firstname.lastname@example.org>, "Peter Zijlstra" <email@example.com>, "X86 ML" <firstname.lastname@example.org>, "Linux Kernel Mailing List" <email@example.com>, "Andy Lutomirski" <firstname.lastname@example.org>, "Ingo Molnar" <email@example.com>, "Borislav Petkov" <firstname.lastname@example.org>, "Mika Penttilä" <email@example.com>, linux-fsdevel <firstname.lastname@example.org>, "Thomas Gleixner" <email@example.com>, "Linus Torvalds" <firstname.lastname@example.org>, "Christoph Hellwig" <email@example.com>, "Al Viro" <firstname.lastname@example.org>, "Peter Zijlstra" <email@example.com>, "Andy Lutomirski" <firstname.lastname@example.org> Subject: Re: use memcpy_mcsafe() for copy_to_iter() (was: Re: [PATCH v3 0/9] Series short description) Date: Tue, 15 May 2018 10:20:11 -0700 [thread overview] Message-ID: <CAPcyv4j6HfqeYhrXrnc-79BGBitWMovtv3-FykthChe7EFtSBQ@mail.gmail.com> (raw) In-Reply-To: <20180515064906.GA29231@gmail.com> On Mon, May 14, 2018 at 11:49 PM, Ingo Molnar <email@example.com> wrote: > > * Dan Williams <firstname.lastname@example.org> wrote: > >> On Mon, May 14, 2018 at 12:26 AM, Ingo Molnar <email@example.com> wrote: >> > >> > * Dan Williams <firstname.lastname@example.org> wrote: >> > >> >> Ingo, Thomas, Al, any concerns with this series? >> > >> > Yeah, so: >> > >> > "[PATCH v3 0/9] Series short description" >> > >> > ... isn't the catchiest of titles to capture my [all too easily distracted] >> > attention! ;-) >> >> My bad! After that mistake it became a toss-up between more spam and >> hoping the distraction would not throw you off. >> >> > I have marked it now for -tip processing. Linus was happy with this and acked the >> > approach, right? >> >> I think "happy" is a strong word when it comes to x86 machine check >> handling. My interpretation is that he and Andy acquiesced that this >> is about the best we can do with dax+mce as things stand today. > > So, how would you like to go about this series? > > To help move it forward I applied the first 5 commits to tip:x86/dax, on a > vanilla v4.17-rc5 base, did some minor edits to the changelogs, tested it > superficially (I don't have DAX so this essentially means build tests) and > pushed out the result. Thanks for that. Technically speaking, you do have dax, but setting up our unit tests is currently not friction free, so I would not expect you to go through that effort. Hopefully we can revive 0day running our unit tests one of these days. > Barring some later generic-x86 regression (unlikely) this looks good to me - feel > free to cross-pull that branch into your DAX/nvdimm tree. > > Or we could apply the remaining changes to -tip too - your call. The remainder patches have developed a conflict with another topic branch in the nvdimm tree, in particular "dax: introduce a ->copy_to_iter dax operation". I think the best course is for me to rebase the remaining 4 on top of tip/x86/dax and carry the merge conflict through the nvdimm tree. > Thanks, > > Ingo Thanks!
prev parent reply other threads:[~2018-05-15 17:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-11 17:10 Dan Williams 2018-05-14 7:26 ` Ingo Molnar 2018-05-14 15:52 ` Dan Williams 2018-05-14 17:53 ` Andy Lutomirski 2018-05-14 19:20 ` Linus Torvalds 2018-05-15 6:49 ` Ingo Molnar 2018-05-15 17:20 ` Dan Williams [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=CAPcyv4j6HfqeYhrXrnc-79BGBitWMovtv3-FykthChe7EFtSBQ@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: use memcpy_mcsafe() for copy_to_iter() (was: Re: [PATCH v3 0/9] Series short description)' \ /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).