mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] jfs updates for 6.3
Date: Wed, 1 Mar 2023 10:02:05 -0600	[thread overview]
Message-ID: <b9d302f5-a4a1-2481-a477-b31f25f8e73c@oracle.com> (raw)
In-Reply-To: <a9466e48-77be-bb9e-bdfe-df8c763d7a76@oracle.com>

On 3/1/23 9:54AM, Dave Kleikamp wrote:
> I should have sent this sooner. I forgot I had this one queued up in 
> linux-next.

Arrgh! Right after sending this I realized I hadn't even pushed my local 
jfs-next branch and it hasn't been in linux-next. It's a very low-risk 
patch, but ignore this request if you'd like to.

Sorry for the noise,
Shaggy

> 
> The following changes since commit 
> 69b41ac87e4a664de78a395ff97166f0b2943210:
> 
>    Merge tag 'for-6.2-rc2-tag' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2023-01-02 
> 11:06:18 -0800)
> 
> are available in the Git repository at:
> 
>    git@github.com:kleikamp/linux-shaggy.git tags/jfs-6.3
> 
> for you to fetch changes up to fad376fce0af58deebc5075b8539dc05bf639af3:
> 
>    fs/jfs: fix shift exponent db_agl2size negative (2023-01-03 10:43:37 
> -0600)
> 
> ----------------------------------------------------------------
> Just one simple sanity check
> 
> ----------------------------------------------------------------
> Liu Shixin via Jfs-discussion (1):
>        fs/jfs: fix shift exponent db_agl2size negative
> 
>   fs/jfs/jfs_dmap.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)

  reply	other threads:[~2023-03-01 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 15:54 Dave Kleikamp
2023-03-01 16:02 ` Dave Kleikamp [this message]
2023-03-01 16:50   ` Linus Torvalds
2023-03-01 18:02 ` pr-tracker-bot

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=b9d302f5-a4a1-2481-a477-b31f25f8e73c@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®