linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: David Niklas <Hgntkwis@vfemail.net>, reiserfs-devel@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH reiser4 support for Linux 5.8.10
Date: Thu, 24 Sep 2020 20:34:19 +0200	[thread overview]
Message-ID: <8c0f0263-1da0-11e9-c7b0-98a0aad9a888@gmail.com> (raw)
In-Reply-To: <20200924132158.38fa279f@Phenom-II-x6.niklas.com>

On 09/24/2020 07:21 PM, David Niklas wrote:
> I'm a kernel dev newbie. Please double check my work if in doubt.
> 
> The patch for reiser4 support for Linux 5.8.1 didn't apply to 5.8.10. It
> needed only a one line change, but because of all the fuzzy matching and
> offset matching I thought I'd make a new one.
> The file that failed to patch is fs/fs-writeback.c. A struct got one of
> it's members removed. As the entire struct was removed by the patch

Hi David,

Precisely speaking, it is not removed, but moved to a header file.

Anyway, I guess that the missing member wasn't used by reiser4, so feel
free to ignore it.

Thanks,
Edward.


  I
> thought it good to ignore the missing member instead of trying to dig up
> what it was used for and why it was removed.
> 
> Thanks,
> David
> 

  reply	other threads:[~2020-09-24 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200728222041.5d88b2e1@Phenom-II-x6.niklas.com>
2020-07-29  2:34 ` PROBLEM: IO lockup on reiserfs FS David Niklas
2020-08-05 16:53   ` Hgntkwis
2020-08-05 19:51     ` Linus Torvalds
2020-08-06  0:01       ` Hgntkwis
2020-08-06  0:37         ` Edward Shishkin
2020-08-17 14:56       ` David Niklas
2020-09-24 17:21         ` PATCH reiser4 support for Linux 5.8.10 David Niklas
2020-09-24 18:34           ` Edward Shishkin [this message]
2020-09-24 19:14             ` David Niklas

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=8c0f0263-1da0-11e9-c7b0-98a0aad9a888@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=Hgntkwis@vfemail.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@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).