linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Van Asbroeck <thesven73@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: kbuild-all@lists.01.org, Al Viro <viro@zeniv.linux.org.uk>,
	Deepa Dinamani <deepa.kernel@gmail.com>,
	David Howells <dhowells@redhat.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Janos Farkas <chexum+dev@gmail.com>,
	Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH v1 2/2] romfs: address performance regression since v3.10
Date: Tue, 23 Jun 2020 13:05:11 -0400	[thread overview]
Message-ID: <CAGngYiUQ_ytR83xRHFBkCOPTuSXvtav8sQrAdg4iC3Up+ncijA@mail.gmail.com> (raw)
In-Reply-To: <202006240015.pGzlVrrz%lkp@intel.com>

On Tue, Jun 23, 2020 at 12:17 PM kernel test robot <lkp@intel.com> wrote:
>
>    ld: fs/romfs/super.o: in function `romfs_largest_blocksize':
> >> fs/romfs/super.c:505: undefined reference to `__moddi3'
>
>  > 505                  if ((device_sz % blksz) == 0)

I can change this to device_sz & (blksz-1) if this patch gets
positive feedback.

  reply	other threads:[~2020-06-23 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  0:45 [PATCH v1 0/2] address romfs performance regression Sven Van Asbroeck
2020-06-23  0:45 ` [PATCH v1 1/2] romfs: use s_blocksize(_bits) if CONFIG_BLOCK Sven Van Asbroeck
2020-06-23  0:45 ` [PATCH v1 2/2] romfs: address performance regression since v3.10 Sven Van Asbroeck
2020-06-23 16:16   ` kernel test robot
2020-06-23 17:05     ` Sven Van Asbroeck [this message]
2020-07-09 12:16   ` Sven Van Asbroeck
  -- strict thread matches above, loose matches on Subject: below --
2020-06-23  0:42 [PATCH v1 0/2] address romfs performance regression Sven Van Asbroeck
2020-06-23  0:43 ` [PATCH v1 2/2] romfs: address performance regression since v3.10 Sven Van Asbroeck

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=CAGngYiUQ_ytR83xRHFBkCOPTuSXvtav8sQrAdg4iC3Up+ncijA@mail.gmail.com \
    --to=thesven73@gmail.com \
    --cc=chexum+dev@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=deepa.kernel@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).