[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130914093343.GA5094@osiris>
Date: Sat, 14 Sep 2013 11:33:43 +0200
From: Heiko Carstens <heiko.carstens@...ibm.com>
To: Russell King <rmk@....linux.org.uk>,
Josh Boyer <jwboyer@...oraproject.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Chris Mason <chris.mason@...ionio.com>,
Mark Fasheh <mfasheh@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [GIT PULL] Btrfs
On Fri, Sep 13, 2013 at 04:58:36PM +0100, Russell King wrote:
> On Fri, Sep 13, 2013 at 11:38:15AM -0400, Josh Boyer wrote:
> > On Fri, Sep 13, 2013 at 11:06 AM, Josh Boyer <jwboyer@...il.com> wrote:
> > > On Fri, Sep 13, 2013 at 8:15 AM, Russell King <rmk@....linux.org.uk> wrote:
> > >> On Fri, Sep 13, 2013 at 07:53:21AM -0400, Josh Boyer wrote:
> > >>> I'm not an ARM expert, so I don't know if ARM should use the
> > >>> asm-generic implementations, or just use __get_user/__put_user in all
> > >>> cases. I've CC'd rmk.
> > >>
> > >> Why do we have uaccess-unaligned.h ? Normally, these kinds of things
> > >> are spawned by architectures which have problems with unaligned accesses,
> > >> ARM being one of them, but afaik we've never need this.
> > >>
> > >> With the kernel-side trapping of unaligned accesses on older hardware,
> > >> we've always dealt with the normal accessor faulting.
> > >>
> > >> From what I can tell in the git history, these unaligned put_user and
> > >> get_user have existed all the way back to the dawn of git use.
> > >>
> > >> Can someone enlighten me why we have them?
> >
> > I somehow fail at email and dropped Russell from CC on accident. Sigh.
>
> You're not the first to do that recently. I'm beginning to think it's
> something someone has written into email clients to make them do in order
> to piss me off. I mean, it's _hard_ to do - you have to manually edit the
> recipients list to just drop one person.
You configured your mail client to generate a "Mail-Followup-To:" header
field which actively asks other mail clients to remove you from replies.
So you only get what you ask for... ;)
I think the mutt "metoo" variable will change that, but I don't know
for sure.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists